Docker
The networks and volumes shared by this server's containers — and why the page is empty on a normal server.
On a server that hosts containers, Docker is where the things containers share live: the user-defined networks they join, and the volumes they keep data in. Individual containers are not managed here — each containerised application has its own container screen.
On a server without containers
Most OSS Panel servers run applications directly on the host. On those, the page is deliberately empty:
Not a container server — "This server doesn't host containers, so it has no Docker networks or volumes." There is nothing to configure and nothing missing; the page exists so the sidebar is the same everywhere.
Containers come from the stack you installed
Whether a server hosts containers is decided at install time by the stack you pick — see Installation. You cannot turn a host-application server into a container server from this screen.
Networks
On a container server, Networks lists the user-defined Docker networks plus Docker's own built-in ones.
The reason they matter is name resolution: "Containers on the same user-defined network can reach each other by name. Docker's built-in bridge can't do that, which is why an app and its database need one of these."
Each network shows the containers attached to it and the ports they publish, or internal only where nothing is exposed. You can create one, attach a site to it, and remove one that nothing is using.
Removal is blocked while it would break something, and the message says which case you are in:
- Containers are still attached — stop or detach them first.
- Sites are set to join this network — change their network first, because removing it now would stop them starting.
Volumes
A volume is "where a container keeps data that has to survive being rebuilt" — the database files, the uploads directory, anything that must outlive the image.
Each volume shows whether it is in use and by how many containers, or Not in use. You can create one and mount it into a site at a path inside its container.
Removing a volume deletes the data in it
The panel refuses while a running container is using it, and warns when sites are configured to mount it — "deleting it now destroys the data they keep in it." An unused volume may still be expected by a stopped container.
Registry credentials
Credentials this server uses to pull private container images live under Integrations → Registries; public images need nothing.
Use your registry username and an access token, not your account password.
Limits and caveats
- This screen is shared infrastructure only. Starting, stopping, rebuilding and reading the logs of one container happen on that application's screens.
- Screenshots of the populated networks and volumes tables are not on this page yet — they need a container-stack server, and are being captured separately. The empty state above is what a standard server shows.
- Removing a network or volume never touches the images themselves.