Comments (19)
Thanks I'll take a look.
It's strange becasue I run a dozen of container and the issue appear only with this pihole-unbound.
Thanks again for the support, I'll keep you updated.
Bonus:
A docker-compose file with bind mounts in place of docker volumes can be useful for several reason :)
from docker-pihole-unbound.
I'm thinking that the default unbound.conf is missing.
This has to be added to the Dockerfile.
from docker-pihole-unbound.
I'm uploading a new latest image to hub.docker.com. Should be finished in a few minutes.
from docker-pihole-unbound.
Issue apper when trying to use bind mounts folder in place of volumes. This is strange cause bind mounted folders exists and has the right permissions.
from docker-pihole-unbound.
You closed this already but I happend to now see this issue (was also away for a while). Did you get this with the latest release? How does your docker-compose.yml look like?
from docker-pihole-unbound.
Yes closed by mistake.
Just to specify that I'm trying to use bind mounts in place of volumes because using the volume as for your template, if I want to edit/re-create the container through Portainer I get this error and I think that with bind volumes this can be solved:
Duplicate mount point: /etc/pihole
Happening with last version and this is how my compose look:
services:
pihole:
container_name: pihole-unbound
image: pluim003/pihole-unbound:latest
hostname: ${HOSTNAME}
domainname: ${DOMAIN_NAME}
ports:
- ${WEB_PORT}:80/tcp
- 53:53/tcp
- 53:53/udp
# - 5335:5335/tcp # Uncomment to enable unbound access on local server
# - 22/tcp # Uncomment to enable SSH
environment:
FTLCONF_LOCAL_IPV4: ${FTLCONF_LOCAL_IPV4}
TZ: Europe/Rome
WEBPASSWORD: ${WEBPASSWORD}
REV_SERVER: true
REV_SERVER_DOMAIN: local
REV_SERVER_TARGET: ${REV_SERVER_TARGET}
REV_SERVER_CIDR: ${REV_SERVER_CIDR}
PIHOLE_DNS_: 127.0.0.1#5335 # Hardcoded to our Unbound server
DNSSEC: "true" # Enable DNSSEC
DNSMASQ_LISTENING: single
volumes:
- /docker-data/pihole-unbound/pihole:/etc/pihole:rw
- /docker-data/pihole-unbound/dnsmasq.d:/etc/dnsmasq.d:rw
- /docker-data/pihole-unbound/unbound:/etc/unbound:rw
- /etc/resolv.conf:/etc/resolv.conf
restart: unless-stopped
from docker-pihole-unbound.
Aha. Can it be that the container is still running when you try to start it? That might cause the duplicate mount point.
from docker-pihole-unbound.
Aha. Can it be that the container is still running when you try to start it? That might cause the duplicate mount point.
Nope, error happens even with stopped container :( It's very strange.
This is the compose in the version that use the volumes (obv almost identical to the above one that use bind mounts):
`version: '3.0'
volumes:
etc_pihole:
etc_dnsmasq:
etc_unbound:
services:
pihole:
container_name: pihole-unbound
image: pluim003/pihole-unbound:latest
hostname: ${HOSTNAME}
domainname: ${DOMAIN_NAME}
ports:
- ${WEB_PORT}:80/tcp
- 53:53/tcp
- 53:53/udp
# - 5335:5335/tcp # Uncomment to enable unbound access on local server
# - 22/tcp # Uncomment to enable SSH
environment:
FTLCONF_LOCAL_IPV4: ${FTLCONF_LOCAL_IPV4}
TZ: Europe/Rome
WEBPASSWORD: ${WEBPASSWORD}
REV_SERVER: true
REV_SERVER_DOMAIN: local
REV_SERVER_TARGET: ${REV_SERVER_TARGET}
REV_SERVER_CIDR: ${REV_SERVER_CIDR}
PIHOLE_DNS_: 127.0.0.1#5335 # Hardcoded to our Unbound server
DNSSEC: "true" # Enable DNSSEC
DNSMASQ_LISTENING: single
volumes:
- etc_pihole:/etc/pihole:rw
- etc_dnsmasq:/etc/dnsmasq.d:rw
- etc_unbound:/etc/unbound:rw
- /etc/resolv.conf:/etc/resolv.conf
restart: unless-stopped
from docker-pihole-unbound.
Hmm... something similar happens in https://www.reddit.com/r/portainer/comments/vrvbrx/docker_volumes_problem_duplicate_mount_point/ Does it complain about another mount point if you change the sequence in your docker-compose.yaml-file?
Could you also run docker-compose --verbose up
from docker-pihole-unbound.
up, any idea ? I've tried with several settings, but didin't find a solution.
@pluim003 how are you actually updating your container without getting this issue ?
volumes:
etc_pihole:
etc_dnsmasq:
etc_unbound:
services:
pihole:
container_name: pihole
image: pluim003/pihole-unbound:latest
hostname: ${HOSTNAME}
domainname: ${DOMAIN_NAME}
ports:
- ${PIHOLE_WEBPORT:-80}:80/tcp #Allows use of different port to access pihole web interface when other docker containers use port 80
- 53:53/tcp
- 53:53/udp
# - 5335:5335/tcp # Uncomment to enable unbound access on local server
# - 22/tcp # Uncomment to enable SSH
environment:
FTLCONF_LOCAL_IPV4: ${FTLCONF_LOCAL_IPV4}
TZ: ${TZ}
WEBPASSWORD: ${WEBPASSWORD}
REV_SERVER: ${REV_SERVER:-false}
REV_SERVER_TARGET: ${REV_SERVER_TARGET}
REV_SERVER_DOMAIN: ${REV_SERVER_DOMAIN}
REV_SERVER_CIDR: ${REV_SERVER_CIDR}
PIHOLE_DNS_: 127.0.0.1#5335 # Hardcoded to our Unbound server
DNSSEC: ${DNSSEC:-false} # Enable DNSSEC
DNSMASQ_LISTENING: single
volumes:
- etc_pihole:/etc/pihole:rw
- etc_dnsmasq:/etc/dnsmasq.d:rw
- etc_unbound:/etc/unbound:rw
- /etc/resolv.conf:/etc/resolv.conf
restart: unless-stopped```
from docker-pihole-unbound.
@zenzip what happens if you don't use the volume etc_unbound? I would guess it will use the default unbound.conf. Or is it then also missing? If so then I'll need to check my Dockerfile to see what's going wrong. On my side everything is running fine.
from docker-pihole-unbound.
@zenzip what happens if you don't use the volume etc_unbound? I would guess it will use the default unbound.conf. Or is it then also missing? If so then I'll need to check my Dockerfile to see what's going wrong. On my side everything is running fine.
Yes this is an option but when I try to update to container the re-deploy fails due duplicates volumes also on etc_pihole and etc_dnsmasq. So removing etc_unbound volume only don't fix that.
from docker-pihole-unbound.
Frankly I don't know what can go wrong. How are you updating the container? I use a script like this:
pi@raspberrypi4:~/pi-hole $ cat upg_pihole_nightly.sh
#!/bin/bash
VANDAAG=$(date +"%Y%m%d")
cd $(dirname $0)
current_pihole_nightly="$(docker inspect pluim003/pihole-unbound:nightly | grep Created)"
docker pull pluim003/pihole-unbound:nightly
pulled_pihole_nightly="$(docker inspect pluim003/pihole-unbound:nightly | grep Created)"
if [[ "${pulled_pihole_nightly}" > "${current_pihole_nightly}" ]];
then echo "There is a new Pihole-nightly, recreating the Pihole-Unbound-nightly"
cp docker-compose.nightly docker-compose.yaml
docker container stop $(docker container ls -q --filter name=pihole-unbound*)
# docker rename pihole-unbound pihole-unbound_${VANDAAG}_$(docker container ls -q --filter name=pihole-unbound*)
/usr/local/bin/docker-compose up -d
fi
And my docker-compose looks like:
pi@raspberrypi4:~/pi-hole $ cat docker-compose.yaml
version: '3.0'
volumes:
etc_pihole:
etc_dnsmasq:
etc_unbound:
log_pihole:
log_unbound:
log_lighttpd:
resolv.conf:
usr_pihole_lists:
ssh:
services:
pihole:
container_name: pihole-unbound
image: pluim003/pihole-unbound:nightly
privileged: true
hostname: ${HOSTNAME}
domainname: ${DOMAIN_NAME}
ports:
- ${WEB_PORT}:80/tcp
- 53:53/tcp
- 53:53/udp
# - 80:80/tcp
- 5335:5335/tcp # Uncomment to enable unbound access on local server
# - 22/tcp # Uncomment to enable SSH
environment:
# network_mode: host
FTLCONF_LOCAL_IPV4: ${FTLCONF_LOCAL_IPV4}
TZ: ${TZ}
WEBPASSWORD: ${WEBPASSWORD}
# WEB_UID: ${WEB_UID}
# WEB_GID: ${WEB_GID}
REV_SERVER: ${REV_SERVER}
REV_SERVER_TARGET: ${REV_SERVER_TARGET}
REV_SERVER_DOMAIN: ${REV_SERVER_DOMAIN}
REV_SERVER_CIDR: ${REV_SERVER_CIDR}
PIHOLE_DNS_: 127.0.0.1#5335 # Hardcoded to our Unbound server
DNSSEC: ${DNSSEC}
DNSMASQ_LISTENING: single
VIRTUAL_HOST: ${VIRTUAL_HOST}
# DNS1: ${DNS1}
FTLCONF_MAXDBDAYS: ${FTLCONF_MAXDBDAYS}
volumes:
- etc_pihole:/etc/pihole:rw
- etc_dnsmasq:/etc/dnsmasq.d:rw
- etc_unbound:/etc/unbound:rw
- log_pihole:/var/log/pihole:rw
- log_unbound:/var/log/unbound:rw
- log_lighttpd:/var/log/lighttpd:rw
# - ./resolv.conf:/etc/resolv.conf
- usr_pihole_lists:/usr/local/bin/my-pihole-lists
- ssh:/root/.ssh
# - /sys/fs/cgroup:/sys/fs/cgroup
restart: unless-stopped
It's recreating nicely every morning a new container. So frankly I'm a bit lost.
from docker-pihole-unbound.
I manage container updates through watchtower, but even if I try just to redeploy the container I get that error. I'm trying re-deploy the container trought portainer, maybe It's a Portainer issue, I'll try with simple cli and docker compose
from docker-pihole-unbound.
Actually I use only the cli. And the container I use is daily updated this way through a cronjob.
from docker-pihole-unbound.
I'm trying to deploying on a new docker host. Even when I try to deploy from scratch I'm getting the same error:
[1701202805] unbound-checkconf[678:0] error: Could not open /etc/unbound/unbound.conf: No such file or directory.
I'm using bind mounts and not volumes.
from docker-pihole-unbound.
I'm uploading a new latest image to hub.docker.com. Should be finished in a few minutes.
really appreciated!
from docker-pihole-unbound.
Finally ... It's working now :)
Thanks!
from docker-pihole-unbound.
from docker-pihole-unbound.
Related Issues (7)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-pihole-unbound.