coryHawkvelt
/
docker-bind
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Resolve error 'the working directory is not writable' by switching into the /tmp/bind directory before executing the bind process

This commit is contained in:
Cory 2020-12-14 11:27:06 +10:30
parent 17161d55f9
commit 5a61e5047b
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
container/entrypoint.sh
View File

@ -3,10 +3,12 @@ OPTIONS=$@
# "Run Time" changes - needed for when creating a *new* directory/first-time volume map
# A great example of this is "/var/cache/bind" for dynamic configs, and mapping it in
# The first time around, it will not be owned by named:named, and thus it won't be writable
mkdir /tmp/bind
chown -R root:named /etc/bind /var/run/named
chown -R named:named /var/cache/bind
chown -R named:named /var/cache/bind /tmp/bind
chmod -R 770 /etc/bind /var/cache/bind /var/run/named
find /etc/bind /var/cache/bind -type f -exec chmod 640 -- {} +
# By default - run in foreground and log to STDERR (console)
# can be changed by running container with: -e "BIND_LOG=-f"
cd /tmp/bind
exec /usr/sbin/named -c /etc/bind/named.conf $BIND_LOG -u named $OPTIONS