👀 Views: 58 💬 Answers: 1 📅 Created: 2025-06-08

docker ubuntu networking bash

I'm upgrading from an older version and I'm a bit lost with I'm working with an scenario with Docker on Ubuntu 22.04 where my custom network bridge configuration is not persisting after a system restart. I created a custom bridge using the following commands: ```bash docker network create --driver bridge my_custom_network ``` After creating the network, I verified it was listed using: ```bash docker network ls ``` The network shows up fine, and I can create containers connected to `my_custom_network`. However, after restarting the Docker service or the entire system, the network disappears from the list. I receive the following behavior when I try to list the networks again: ``` behavior response from daemon: bridge "my_custom_network" not found ``` I've checked the Docker configuration in `/etc/docker/daemon.json`, but I haven’t changed anything that would affect network persistence. It contains just the default settings: ```json { "storage-driver": "overlay2" } ``` I've also tried adding a network restore policy in my Docker Compose file like this: ```yaml version: '3' services: my_service: image: my_image networks: - my_custom_network networks: my_custom_network: external: name: my_custom_network ``` But even with this setup, the custom network is still gone after a reboot. I've ensured Docker is set to start on boot with: ```bash sudo systemctl enable docker ``` What am I missing? Is there a specific configuration I need to apply for custom networks to continue across reboots? Any insights or suggestions would be greatly appreciated. I've been using Bash for about a year now. Any advice would be much appreciated. Has anyone dealt with something similar?