Skip to content

open: /etc/bind/named.conf: permission denied - cannot deploy in Portainer #111

Description

@shalak

I'm having some issues when deploying from sameersbn/bind:latest using Portainer that runs on OpenMediaVault.

I configured /data/ to be mapped to /src/dev-disk-by-uuid-XXX/sharedFolder/containers/bind, the container doesn't start. Log says:

07-Feb-2021 22:12:18.056 loading configuration from '/etc/bind/named.conf'
07-Feb-2021 22:12:18.056 open: /etc/bind/named.conf: permission denied
07-Feb-2021 22:12:18.064 loading configuration: permission denied
07-Feb-2021 22:12:18.064 exiting (due to fatal error)

The container did succeed to create some files, here's what I see on OpenMediaVault:
image

User mirek is the owner of the /src/dev-disk-by-uuid-XXX/sharedFolder/containers/bind directory. The user systemd-timesync has UID 101 and systemd-journal has GID of 101.

I tried setting the BIND_USER to mirek - did not help. When I do it, I only see the following log and no files are created in volume:

chown: invalid group: 'root:mirek'

What am I missing here? How can I force the docker-bind to always use user mirek and group users?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions