Unable to update unbound container with fixed IP address

[xorguy]

Hi.

Tried to perform an update to a unbound container, with fixed IP set at the compose file and when the container restarted after updating it was unable to start, error was address and port in use.
I had to perform a docker compose down unbound and then start again.

Compose for the unbound is like this:

unbound: container_name: unbound image: madnuttah/unbound:latest hostname: unbound domainname: net.lan ports: - 8114:5335/tcp - 8114:5335/udp networks: default: ipv4_address: "10.10.1.73" environment: TZ: Europe/Madrid ServerIP: 10.0.0.53 VIRTUAL_HOST: unbound.net.lan volumes: - ../settings/unbound-docker/unbound.conf:/usr/local/unbound/unbound.conf:rw #Your local path to Unbound - ../settings/unbound-docker/conf.d/:/usr/local/unbound/conf.d/:rw - ../settings/unbound-docker/log.d/unbound.log:/usr/local/unbound/log.d/unbound.log:rw - ../settings/unbound-docker/zones.d/:/usr/local/unbound/zones.d/:rw restart: unless-stopped healthcheck: test: /usr/local/unbound/sbin/healthcheck.sh interval: 60s retries: 5 start_period: 15s timeout: 30s

[dgongut]

Hi! Could you test with 3.2.0 tag?

[xorguy]

Hi. I was unable to test it before. I just tried it now with latest official 3.2.1 and the container keeps failing to restart when I try to update from bot.

[dgongut]

No problem, I will try to keep looking for a solution. Thanks for the feedback!