isc-projects / bind9-docker Goto Github PK

Trying to do operations like chown/chmod after VOLUME has been declared does not work.

From the docker documentation at: https://docs.docker.com/engine/reference/builder/#volume:

Changing the volume from within the Dockerfile: If any build steps change the data within the volume after it has been declared, those changes will be discarded.

Please change the Docker file FROM:

VOLUME ["/etc/bind", "/var/cache/bind", "/var/lib/bind", "/var/log/bind"]

RUN mkdir -p /etc/bind && chown -Rvf root:bind /etc/bind/ && chmod 755 /etc/bind
RUN mkdir -p /var/cache/bind && chown -Rvf bind:bind /var/cache/bind && chmod 755 /var/cache/bind
RUN mkdir -p /var/lib/bind && chown -Rvf bind:bind /var/lib/bind && chmod  755 /var/lib/bind
RUN mkdir -p /var/log/bind && chown -Rvf bind:bind /var/log/bind && chmod 755 /var/log/bind
RUN mkdir -p /run/named && chown -Rvf bind:bind /run/named && chmod 755 /run/named

TO:

RUN mkdir -p /etc/bind && chown -Rvf root:bind /etc/bind/ && chmod 755 /etc/bind
RUN mkdir -p /var/cache/bind && chown -Rvf bind:bind /var/cache/bind && chmod 755 /var/cache/bind
RUN mkdir -p /var/lib/bind && chown -Rvf bind:bind /var/lib/bind && chmod  755 /var/lib/bind
RUN mkdir -p /var/log/bind && chown -Rvf bind:bind /var/log/bind && chmod 755 /var/log/bind
RUN mkdir -p /run/named && chown -Rvf bind:bind /run/named && chmod 755 /run/named

VOLUME ["/etc/bind", "/var/cache/bind", "/var/lib/bind", "/var/log/bind"]

BIND 9.16 is EOL in April 2024

Can the default branch be set to a supported version instead of 9.16?

See https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch for more info.

The Docker Hub page points to this repo as the source, but I see there are other project for Docker under GitLab which are more

https://gitlab.isc.org/isc-projects/bind9-docker
https://gitlab.isc.org/isc-projects/images

Which of these projects should be followed for published containers ?
How often are releases for the containers updated? I see that as of the creation of this issue 9.16.20 is viable in the Ubuntu PPA https://launchpad.net/~isc/+archive/ubuntu/bind

Currently the containers are versioned with tags like 9.16, a suggestion would be to make these tags follow the Bind9 release version like 9.16.20. This helps to prevent unwanted / tested updates in environments

"not using config file logging statement for logging due to -g option" when start docker container from instructions:

docker run \
        --name=bind9 \
        --restart=always \
        --publish 53:53/udp \
        --publish 53:53/tcp \
        --publish 127.0.0.1:953:953/tcp \
        --volume /etc/bind \
        --volume /var/cache/bind \
        --volume /var/lib/bind \
        --volume /var/log \
        internetsystemsconsortium/bind9:9.16

It would be useful if this image could use an arbitrary uid and gid (perhaps using the scheme in https://github.com/wastrachan/docker-bind).

This would make it easier to use the image with bind mounts on a host where the uid/gid of the bind user are different from those inside the container.

Hi @oerdnj hope you're doing well.

Recently I'm trying to run a few configs and tests using bind9.16 but after doing a docker pull from the docker hub container registry

it seems like you're only building the docker image for linux/amd64. so if I try to create a lab in my local machine to do validations I got the following message :

! bind9 The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s

This happens because you're not using docker buildx build --platform linux/amd64,linux/arm64 .

I was also wondering what are you currently using to push to the public url

I have fixed this by buildin the image locally, but it would be great to add a GitHub action pipeline to do this automatically 😄

Regards,
H

It would be nice if nc would be contained in the docker image, so a health check can easily be configured.

For the record, in my docker-compose.yml I used:

  healthcheck:
    test: ["CMD-SHELL", "nc -z localhost 53 || exit 1"]

but since a few versions it fails because nc cannot be found any more. If you agree, I can probably provide a PR.

Hi Sir, thanks for the bind9 in docker, I would like to feedback not sure why I got the below message when I try to build the image
Step 8/17 : RUN add-apt-repository -y ppa:isc/bind
---> Running in 8a1651a18b0f
Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:2 http://ppa.launchpad.net/isc/bind/ubuntu focal InRelease [24.3 kB]
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Get:6 http://ppa.launchpad.net/isc/bind/ubuntu focal/main amd64 Packages [3650 B]
Fetched 28.0 kB in 1s (30.7 kB/s)
Reading package lists...
Removing intermediate container 8a1651a18b0f
---> 43082384c031
Step 9/17 : RUN apt-get -qqqy update && apt-get -qqqy dist-upgrade && apt-get -qqqy install bind9=$DEB_VERSION bind9-utils=$DEB_VERSION
---> Running in 789b2d64d12b
E: Version '1:9.16.19-1+ubuntu21.04.1+isc+1' for 'bind9' was not found
E: Version '1:9.16.19-1+ubuntu21.04.1+isc+1' for 'bind9-utils' was not found

Thanks

Best Regards
Kheng Soon

Might be helpful if the latest stable release was also pull-able via a stable tag. It would be particularly helpful for people who use Watchtower to update containers automatically.

Hi,I＇m using Bind Dockerfile 9.18,but while I was building mirroring,I found that the repo resource doesn't include 9.18.11-1+ubuntu22.04.1+isc+2 and isc+1.

when I try to build the image

=> [internal] load metadata for docker.io/library/ubuntu:jammy

[ 8/14] RUN apt-get -qqqy install bind9=1:9.18.11-1+ubuntu22.04.1+isc+2 bind9utils=1:9.18.11-1+ubuntu22.04.1+isc+2:
#0 0.750 E: Version '1:9.18.11-1+ubuntu22.04.1+isc+2' for 'bind9' was not found
#0 0.750 E: Version '1:9.18.11-1+ubuntu22.04.1+isc+2' for 'bind9utils' was not found
Dockerfile:20
18 | RUN apt-get -qqqy update
19 | RUN apt-get -qqqy dist-upgrade
20 | >>> RUN apt-get -qqqy install bind9=$DEB_VERSION bind9utils=$DEB_VERSION
21 |
22 | # Now remove the pkexec that got pulled as dependency to software-properties-common
error: failed to solve: process "/bin/sh -c apt-get -qqqy install bind9=$DEB_VERSION bind9utils=$DEB_VERSION" did not complete successfully: exit code: 100
FATA[0001] no image was built

Hello There,

ive tried to update my bind container to 9.19.
Whenever i try to use 9.18 or 9.19 it dont work. Before it was a working 9.19.
I can't find any reason for it, it just tells bind exited with code 0.
If i use 9.16 it's back working. What might be the reason? Thx

docker-compose:

`
version: '3.8'

services:
bind:
container_name: bind
user: 1000:100
image: internetsystemsconsortium/bind9:9.19
restart: unless-stopped
volumes:
- /etc/localtime:/etc/localtime:ro
- /etc/timezone:/etc/timezone:ro
- ./volume/config:/etc/bind
- ./volume/records:/var/lib/bind
- ./volume/cache:/var/cache/bind
- ./volume/log:/var/log
networks:
- default
ports:
- "10.10.10.1:53:53/udp"
- "10.10.10.1:53:53/tcp"

networks:
default:
driver: bridge
`