Hi folks,

I created a some additional networking in a docker compose file and upon deploying it my unraid server was inaccessible. I had to press the power button to start the shutdown process.

On starting the server I can only start the array if the docker service is stopped and I think it is because the network I added in the compose file broke my docker networking config. If I start the docker service the GUI/admin panel fails to load and the server becomes inaccessible again.

The compose file is:

networks:

adguard:

driver: bridge

ipam:

config:

- subnet: 192.168.0.0/24

gateway: 192.168.0.1

services:

adguard:

image: adguard/adguardhome:latest

container_name: adguard

ports:

- 5443:5443/udp

- 5443:5443/tcp

- 8853:8853/udp

- 853:853/udp

- 784:784/udp

- 853:853/tcp

- 3008:3000/tcp

- 53:53/udp

- 53:53/tcp

volumes:

- /mnt/user/appdata/adguard/conf:/opt/adguardhome/conf

- /mnt/user/appdata/adguard/work:/opt/adguardhome/work

restart: unless-stopped

networks:

adguard:

ipv4_address: 192.168.0.53


This is my docker settings page:



Route table is here:

Could someone please help with getting the docker networking config back to something sensible?

My LAN IP range is 192.168.0.1/24

Edited January 23Jan 23 by fuzzaldrin

This is the contents of the docker.cfg file in the flash drive:

I've removed the compose file for that service and tried starting docker and the same behaviour is happening :(

After rebooting I can see this in the logs just as I started the docker service:

Jan 23 21:05:50 teapot rc.docker: container adguard has an additional network that will be restored: adguard_adguard

This is weird because I deleted that compose file from compose manager plugin before starting the docker service so this is lingering somewhere on the system.

Edited January 23Jan 23 by fuzzaldrin

🎉 RESOLVED 🎉

OK so I managed to pinpoint that the container was still registered in docker however without any access to the console or terminal I couldn't remove the container or the offending network.

I created a script in the User Scripts plugin to run every 2 minutes with the following:
#!/bin/bash

docker stop adguard

docker container rm adguard -f

docker network rm adguard_adguard

echo Finished

echo if an error shows above, nothing was removed

I started the docker service from the setting and could immediately see the permanent ping I had running on the unraid admin console drop, waited for the script to run on schedule and immediately I saw the ping successfully respond. I opened a new tab and loaded the unraid admin console/GUI successfully!

For the sake of anyone else that may run into this niche issue, I've included the output of the user script below, it shows the script run before the docker service was started and obviously failing to remove the network and container and then subsequently shows the script successfully run and delete the network and container:

Script Starting Jan 23, 2026 21:36.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Finished
if an error shows above, nothing was removed
Script Finished Jan 23, 2026 21:36.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt

Script Starting Jan 23, 2026 21:38.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt

adguard
adguard
adguard_adguard
Finished
if an error shows above, nothing was removed
Script Finished Jan 23, 2026 21:38.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/docker_remove_adguard/log.txt