This options works well until last update, actually if I select Bridge Mode, and use "--network my-net" ( my-net is my own personal net), webGUI refuses to use it.
Perhaps, in the drop-down menu, "my-net" must appears, but actually not.
This options works well until last update, actually if I select Bridge Mode, and use "--network my-net" ( my-net is my own personal net), webGUI refuses to use it.
Perhaps, in the drop-down menu, "my-net" must appears, but actually not.
I am having the same problem
I supose is a common problem.
perhaps if some developer read this, can be repaired quickly.
When the network options were added they were intended for macvlan, not custom networks. We are closely to release omv5 and docker plugin will not likely move onto it. And if it does it will be as it is now, unless someone wants to come forward and fix this or add features.
Portainer should be used as default docker management.
And idea for the plugin in my head would be to strip it down to just the bare minimum container panel viewer with just start,
Stop and remove containers buttons. Managing should be done by compose, which gives you effortless maintain and backup of your containers.
Same here!
Followed TDL's tutorials, can access OMV and Nextcloud from home netwerk, and when accessing from WAN I see this nginx screen indicating that the server is up.
A simple but unsafe by-pass is simply redirecting (port-forwarding) traffic from WAN to 192.168.XXX.XXX:444. Then directly connecting to my IP using the Nextcloud app on my phone ( https://xxx.xxx.xxx.xxx:REDIRECT PORT) .. unfortunately, it's an unsafe connection this way.
Every time I add "--network my-net" in any container in the field extra-arguments, running the container produces an error (125) as seen in the first post above.
When the network options were added they were intended for macvlan, not custom networks. We are closely to release omv5 and docker plugin will not likely move onto it. And if it does it will be as it is now, unless someone wants to come forward and fix this or add features.
Portainer should be used as default docker management.
And idea for the plugin in my head would be to strip it down to just the bare minimum container panel viewer with just start,
Stop and remove containers buttons. Managing should be done by compose, which gives you effortless maintain and backup of your containers.
ok, but this option works previosly, can you please correct it until OMV5 arrives and for users that still use OMV4.
Thanks in advanced.
That’s because docker update their run options. The error is from docker, not allowing default mixed with custom network.
This is docker v19 right?
YES, not possible a patch?
like option to select my-net on network pull-menu?
Client: Docker Engine - Community
Version: 19.03.0
API version: 1.40
Go version: go1.12.5
Git commit: aeac9490dc
Built: Wed Jul 17 18:14:03 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.0
API version: 1.40 (minimum version 1.12)
Go version: go1.12.5
Git commit: aeac9490dc
Built: Wed Jul 17 18:12:33 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.6
GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc:
Version: 1.0.0-rc8
GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
docker-init:
Version: 0.18.0
GitCommit: fec3683
Alles anzeigen
But...look at the error is from docker. What happens if you select none as network and add your extra arg?
you have also an option to connect the container to a network, in the network grid.
Thanks subzero79! That worked for me!
So what I did is:
1. set up duckdns, letsencrypt, nextcloud and nextclouddb (=mariadb) without "--network my-net" as extra-argument.
2. then I clicked on Docker -> Network and then the CREATE button.
3. Then I created a network called "test-network" with: driver: MACVLAN, subnet: 172.19.0.0/16 (I basically added one number because 192.17 and 18 already existed), and added all containers to it.
I just hope that I didn't accidentally bypass the reversed proxy in doing this..
Same problem here.
I have used "--network=docker" to create my own subnets where host names will be dynamically resolved. Problematic with the gui is also that if you started the container using "--network=docker" as extra argument in bridged mode, the next edit will show network mode "Docker". If you save the editor without changing it back to "Bridge", it will fail and reset all port configs.
Now this trick with "--network=docker" does not work anymore. What happened is that my Nextcloud container disappeared due to the error message in the opening post.
Why is the additional network adapter not supported in the gui? How could we fix this problem?
manually join the containers in the network tab of the gui
manually join the containers in the network tab of the gui
Is this somehow possible to do before start of the container?
Thanks for this hint!
NO.
you need to create the container without --network my-net and once is created and working , then you can change on the network tab.
PD: Is annoying but developers do not want to correct because docker pluging do not exist on upcoming OMV5.
Hey guys!
Recently tried to set up Nextcloud remote access based on tutorial provided by Techno-dad life chanel.
As it seemed to me all went good I paased all the stages reflected in tuttorial quite well, but when it was needed to add extra argument "--network yournetwork-net", server encountered with some issue, as I learnt this happened due to some recent updates, and I started searching for solution which I found here. So a created MACVLAN network in Docker and add all containers such as nextcloud, duckdns etc manualy.
now if i try to login via webinterface I have the following reply, pls refer to attachment.
Also I heve installed the app to my Iphone, and if I try to connect via nextcloud app, server says either "access forbidden no token state" or "access forbidden csrf check failed"
Any hints guys wat i did wrong?
should any addinitional info needed pls let me know, coz I quite new here and likely don't do things properly.
You have to create a user - defined bridge network in docker not a macvlan
You have to create a user - defined bridge network in docker not a macvlan
Hi Morlan, thx for prompt reply. Pls see below my docker network configuration. I have bridge network which is plombir-net. Moreover as was adviced few posts above I created macvlan: test-network hoping this would sort out the problem. Based on print scereen clould you pls eleborate my next steps?
Delete the macvlan and add the containers to plombir-net
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!