view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Try adding
USER root
before the mkdir.Also, just in general, when debugging container files, I comment out the failing line and set my command to
tail -F /dev/null
, then you can build and run the container andexec <container> bash
and try to manually run the commands that are failing.This is a very useful trick, thanks.
The problem was with the chmod, I changed it to include execute permissions for the user (764) and it worked. I'm also running named with a
-u bind
flag in "ENTRYPOINT" for insurance.