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 and exec <container> bash and try to manually run the commands that are failing.
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.
As long as you’re not relying on RAID as your backup. Don’t know why so many people struggle with understanding, RAID is not a backup. It’s a solution to ensure uptime in the face of a lost disk. I would guess most selfhosters shouldn’t be concerned with uptime. Use Borg or restic. Or if you are going to use zfs or btrfs then have a completely separate drive or pool where snapshots are stored.
Chatgpt hope it helps looks like the permissions and ownership setup in your CONTAINERFILE might have a minor issue. Specifically, the chmod command you’re using might not be setting the directory permissions correctly. Directories usually need execute permissions for traversal. Here’s a refined version of your CONTAINERFILE to ensure the bind user has the correct permissions:FROM debian
RUN apt-get install -y bind9 bind9-dnsutils bind9-libs bind9-utils sudo
Configure permissions for BIND directories
RUN mkdir -p /var/cache/bind /var/lib/bind /var/log/bind RUN chown -R bind:bind /var/cache/bind /var/lib/bind /var/log/bind RUN chmod 770 /var/cache/bind /var/lib/bind /var/log/bind
Create and configure log files
RUN touch /var/log/bind/default.log /var/log/bind/update_debug.log /var/log/bind/security_info.log /var/log/bind/bind.log RUN chown -R bind:bind /var/log/bind RUN chmod 660 /var/log/bind/*.log
Set the default command arguments for the named executable
CMD [“-g”]Changes Made:Directory Permissions: Changed the permissions of the directories to 770 to ensure that the bind user can read, write, and execute (necessary for accessing the directory).Log File Permissions: Adjusted the log file permissions to 660 to ensure that only the bind user (and group, if applicable) can read and write.Explanation:chmod 770: Grants read, write, and execute permissions to the owner and the group. The execute permission is necessary for directories so that users can access their contents.chmod 660: Grants read and write permissions to the owner and the group for the log files, which is typically sufficient.Give this updated CONTAINERFILE a try and see if it resolves the permissions issue you’re encountering
Do you need to serve an actual public like a website does? If not then you shouldn’t be exposing any fucking services except for wireguard for you and your handful of users.
I’ve never set up a VPN. I’ve connected to them for work, sure, and I’ve dealt with port forwarding for games back in the day. Is it much trickier? Their site makes it sound pretty easy.
If there were no religions I’d figure that human race is one where tribalism can’t catch on as well, in which case there would probably be a lot less organized violence like wars.
Individual crimes are always going to happen with or without religion. Crimes generally have real tangible punishments and there are still criminals. Imaginary punishments aren’t going to do much to stop them.
nginx is mature and has a lot of support online. A lot of server projects assume you’re using nginx, as well. I’ve only ever seen caddy instructions on newer projects and even then, they usually also have nginx instructions.
You might want to stick to young adult stuff. It will have less objectionable content, I think. As for a real suggestion try Sabriel by Garth Nix and if you like it there are others in the series.
kbin.life
Oldest