Since upgrading I can no longer get any new containers to use Gluetun as the variable network_mode: in the YAML or even custom compose import has no effect.
It always overwrites to networks - default
If I create the container in Portainer stack i have no issues or even from terminal via ssh, but then the app is unavailable in the GUI APPS list
Now started through ssh execution docker compose up (Including containers managed by Dockge), it cannot be displayed in the dashboard and cannot be managed.
We will fix this issue in the next version. For the current version, you can work around it by modifying the network configuration in the YAML editor. You can refer to the configuration below:
Yeah, I manage all my containers with Dockge, and they do not show up in the UI. It is a bug in the 1.7.0 release, and they said they will fix it. It doesn’t really bother me because I don’t launch any of my services from the ZimaOS UI, but I can see how it is frustrating for some people who do.
In fact, it’s better that way.
This allows applications to be managed and deployed with management tools such as Portainer or Dockhand or via the SSH terminal.
ZimaOS does not want to appropriate and manage them now.
I just tested it and it’s really better.
There are applications that are much easier to manage with Portainer or Dockhand for example.
In fact, don’t change anything at this level. I dreamed of being able to use several management tools.
All that does is change the name of the default network; the same issue persists. Other apps are not able to use the network_mode: “service:gluetun” line of reasoning…