the-kube-way / nsd Goto Github PK

SSIA: could you consider updating the image to 4.8.0 ?

No matter how I set the environment variable UID and GID, the container starts as 991 and then fails because it's unable to chown the mounted volumes. Is there anything you would recommend I test on my side to verify if this is a user error or not?

Steps to recreate:

1. Create docker-compose.yml

version: '3.7'

services:
  nsd:
    container_name: nsd
    restart: always
    image: ghcr.io/the-kube-way/nsd:test
    read_only: true
    tmpfs:
      - /tmp
      - /var/db/nsd
    volumes:
      - /opt/nsd/conf:/etc/nsd:ro
      - /opt/nsd/zones:/zones
      - /opt/nsd/keys:/keys:ro
    ports:
      - "8554:53"
      - "8554:53/udp"

2. Set environment variables

export UID=${UID}
export GID=${GID}

3. Start the container

docker-compose up

The error I am getting:

user@localhost:/opt/nsd$ docker logs -f nsd
+ UID=991
+ GID=991
+ chown -R 991:991 /var/db/nsd /tmp
chown: /var/db/nsd: Operation not permitted
chown: /var/db/nsd: Operation not permitted
chown: /tmp: Operation not permitted
chown: /tmp: Operation not permitted

System information:

OS: Ubuntu 20.04.3 LTS
Docker version 20.10.11, build dea9396
docker-compose version 1.29.2, build 5becea4c

Please let me know if you are able to recreate this.

Hey @fl42,

Thanks for the work! I finally got it to work in my kubernetes cluster, although there have to be some changes made for kubernetes version 1.25 that I could provide a pull request for in the future.

My question is about configuring zones, and if it is possible to define multiple zones in the nsd-conf. I found some examples online, but they just use a format that seems to be invalid for yaml syntax (having duplicate keys). Do you know how I could provide multiple zones?

My use case is having a zone dev and a zone prod on the same nsd-server