Docker Network Manager

Manage Docker networks directly from the Unraid web UI.

Install

Unraid Community Applications

In Unraid, go to Apps and search for:

docker networks

Unraid Plugin Manager

In Unraid, go to Plugins → Install Plugin and paste:

https://raw.githubusercontent.com/mstrhakr/docker.networks/main/docker.networks.plg

Basic Usage

1. Open Docker → Networks.

2. Click Refresh to load current networks.

3. Click + Create Network to add a new network.

4. Use Edit to update network description/metadata.

5. Use Manage to connect or disconnect containers.

6. Use Delete to remove custom networks.

Default/system networks (for example bridge, host, none, and parent-interface system networks like bond0/eth0) are protected and cannot be deleted.

Troubleshooting

• If the UI looks stale after an update, do a hard refresh: Ctrl+Shift+R.

• If network actions fail, ensure Docker is running on Unraid.

Support

• Issues: GitHub Issues

Edited June 19Jun 19 by mstrhakr

FYI This is pending some kind of manual verification for plugins before it will be listed in the CA app store. I've submitted the request an hour or two ago and now we are waiting. Of course manually installing and updating via the Plugins tab is always an option.

This is now available in CA.

Edited June 13Jun 13 by mstrhakr

will this also show any networks that were created via cli?

18 hours ago, JudasD said:

will this also show any networks that were created via cli?

Yes, its basically doing docker network list and getting all the networks available on the system. It also currently shows system networks also but I'll be adding an option to hide those if that is preferred.

What are the 3 dots for in the Actions column?

They don’t seem to have any function.

They tell me i need to test at multiple window sizes lmao. But there are two more buttons there, manage which allows adding and removing containers from each network, and delete which allows you to delete a network with no connections. I will get this fixed, sorry about that, for now you can zoom out with `[CTRL]+[-]` to see the buttons.

2 minutes ago, mstrhakr said:

They tell me i need to test at multiple window sizes lmao. But there are two more buttons there, manage which allows adding and removing containers from each network, and delete which allows you to delete a network with no connections. I will get this fixed, sorry about that, for now you can zoom out with `[CTRL]+[-]` to see the buttons.

No keyboard (it’s a iPhone) but a pinch doesn’t work.

On 6/16/2026 at 9:07 PM, wgstarks said:

No keyboard (it’s a iPhone) but a pinch doesn’t work.

I forgot to update you, but this should be resolved with some mobile specific layout work. It should be completely usable on mobile now.

Hi all, i dont know if anyone else is having this problem, but when i have the plugin set to Docker tab, the page is empty any ideas?, im using firefox.

On 7/14/2026 at 4:25 AM, Del81 said:

Hi all, i dont know if anyone else is having this problem, but when i have the plugin set to Docker tab, the page is empty any ideas?, im using firefox.

Not sure why that's happening, try doing a hard refresh in your browser. [CTRL]+[SHIFT]+[R] If that doesn't fix it please provide the unraid version you are on and I'll see what I can figure out.

Hi thank you for your suggestion, that has not worked, i am running UnRAID 7.3.2
I greatly appreciate your help

Just wanted to report a bug.

I wish I could remember the steps leading up to what happened but long story short, using the docker network to move multiple docker containers to/from different networks broke my docker network configs.

It left 26 dockers in the "pending" entry in docker networks. This prevented docker containers from properly connecting to the network and left them unusable on that network.

Deleting the network with CLI did nothing to remedy this. Completely deleting my docker.img file did nothing to help. Doing the previous tasks paired with a system restart did not work.

Putting the dockers on a different network allowed them to work, but putting them back on the original network resulted in issues, mainly: endpoint with name DOCKER_NAME already exists in network NETWORK_NAME.

I managed to fix this for the most part by reinstalling all of my docker containers back to the affected network, and then I had to use docker network plugin to disconnect them from the docker network before I could reattach them without issues.

For some reason, I cannot get these last two containers out of pending.

EDIT: figured out why they are left in "pending" at least for me. For the docker containers on the template page, I had to click open the advanced view and clear out post arguments. Worked flawlessly after that

Edited September 18Sep 18 by Power_Stone

On 9/19/2026 at 6:54 AM, Power_Stone said:

Just wanted to report a bug.

I wish I could remember the steps leading up to what happened but long story short, using the docker network to move multiple docker containers to/from different networks broke my docker network configs.

It left 26 dockers in the "pending" entry in docker networks. This prevented docker containers from properly connecting to the network and left them unusable on that network.

Deleting the network with CLI did nothing to remedy this. Completely deleting my docker.img file did nothing to help. Doing the previous tasks paired with a system restart did not work.

Putting the dockers on a different network allowed them to work, but putting them back on the original network resulted in issues, mainly: endpoint with name DOCKER_NAME already exists in network NETWORK_NAME.

I managed to fix this for the most part by reinstalling all of my docker containers back to the affected network, and then I had to use docker network plugin to disconnect them from the docker network before I could reattach them without issues.

For some reason, I cannot get these last two containers out of pending.

EDIT: figured out why they are left in "pending" at least for me. For the docker containers on the template page, I had to click open the advanced view and clear out post arguments. Worked flawlessly after that

Can confirm this bug.

These post arguments are causing the container recompiles to fail as well. Deleting all the post arguments from all containers impacted by this plugin fixes the issue.

Recommend users no longer use this plugin until devs remove all post arguments.

Edited September 23Sep 23 by DCCXVIII

Thanks to everyone who reported the stuck “pending” entries, duplicate-endpoint errors, and failed container updates. The plugin’s use of Post Arguments for network persistence was the wrong approach, and I’m moving away from it entirely.

I’ve committed changes for the next release:

• Unraid 7.4 and newer: additional attachments use Unraid’s native Additional Networks field. For prerelease builds, this requires 7.4.0-beta.1.2 or newer, which includes the container-update restoration fix.

• Earlier Unraid versions: container attachment changes are disabled. Network inspection, creation, and metadata editing remain available.

• Post Arguments are left alone: the plugin will no longer add, remove, or migrate network commands there.

If reconnect commands are detected in existing Post Arguments, a warning will identify the affected containers. Attachment changes through the plugin will be blocked for those containers to avoid adding conflicting configuration. Those commands may have been added manually, so the plugin will not assume ownership or remove them.

This does not automatically repair existing Post Arguments. Review affected containers in Unraid’s container editor, and don’t indiscriminately clear unrelated arguments. Deleting networks or rebuilding docker.img does not remove commands saved in container templates.

The changes also correct pending counts and distinguishes attachments awaiting container recreation from live connections. A plain container start does not apply newly saved Additional Networks.

On 7/17/2026 at 3:48 AM, Del81 said:

Hi thank you for your suggestion, that has not worked, i am running UnRAID 7.3.2
I greatly appreciate your help

This is also fixed but the fix is in the latest beta of Compose Manager Plus, the issue was related to the editor modal tabs causing the Network tab to remain hidden when selected.