I realized after upgrading to 6.8 that my LetsEncrypt reverse proxy had stopped working and that a bunch of my dockers started disappearing. I found that this was due to custom docker networks unable to be specified in the extra params with --network. After some research I found that I can make a docker network container to appear in the drop down. I ran 

docker network create container:letsencrypt

which made the network and got rid of the "network does not exist" error when I tried to start a docker using the --network flag. Now I have another issue when attempting to use the network.. The new error is:

/usr/bin/docker: Error response from daemon: conflicting options: port publishing and the container type network mode.

I was unable to find anything about this issue. It looks like it might be asking me to remove the port mappings from the dockers but I don't think that would let me use the docker.. Any ideas? 

I removed the ports from a docker container to test and it let me start the docker with the network selected but the functionality of the docker is no longer there since I cannot get into it without a port. Is anyone using custom docker networks on 6.8 successfully? 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='apacheguacamole' --net='container:letsencrypt' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'OPT_MYSQL'='Y' -e 'OPT_MYSQL_EXTENSION'='N' -e 'OPT_SQLSERVER'='N' -e 'OPT_LDAP'='N' -e 'OPT_DUO'='N' -e 'OPT_CAS'='N' -e 'OPT_TOTP'='N' -e 'OPT_QUICKCONNECT'='N' -p '9876:8080/tcp' -v '/mnt/user/appdata/ApacheGuacamole':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'jasonbean/guacamole' 
/usr/bin/docker: Error response from daemon: conflicting options: port publishing and the container type network mode.
See '/usr/bin/docker run --help'.

The command failed.

Is what I get when trying to use the docker network. 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='apacheguacamole' --net='container:letsencrypt' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'OPT_MYSQL'='Y' -e 'OPT_MYSQL_EXTENSION'='N' -e 'OPT_SQLSERVER'='N' -e 'OPT_LDAP'='N' -e 'OPT_DUO'='N' -e 'OPT_CAS'='N' -e 'OPT_TOTP'='N' -e 'OPT_QUICKCONNECT'='N' -v '/mnt/user/appdata/ApacheGuacamole':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'jasonbean/guacamole' 
6d183fe75c50fbd4f6b3186fbdeecb9e964ebc76958e25a2ea2f0356d8b832f5

The command finished successfully!

Is what I get when I remote the ports form the template. 

 

Is this intended? How else am I supposed to access the docker without the ports being mapped? 

Maybe this can help

28 minutes ago, bonienl said:

Maybe this can help

I did try the network creation via cli due to Unraid 6.8 but that is when the port issue occurred. It may be because of the network my letsencrypt is set to? In that guide what network setting do you have the network set to on the VPN container? 

 

I still cannot create a docker with Custom: container:letsencrypt as the network and containing ports with the letsencrypt docker set to Host or Bridge as its network.  

4 minutes ago, Chandler said:

In that guide what network setting do you have the network set to on the VPN container? 

I am not using any user defined networks and can't really comment on the workaround given in the link.

My understanding is that some users have this working. Maybe somebody else may jump in and help.

13 minutes ago, bonienl said:

I am not using any user defined networks and can't really comment on the workaround given in the link.

My understanding is that some users have this working. Maybe somebody else may jump in and help.

Got it. I am sure someone else has it working as well.. Thanks for the input. 

 

I just tried deleting and recreating the network I had tried it on a new container but still get the port mapping issue. Anyone else have any ideas? 

I notice in the link above it calls the --link parameter in the nginx docker to link the deluge to the vpn and pass port 8112. I tried running a link between my letsencrypt and apacheguacamole dockers but I get a failed message saying linking is only for dockers on a custom user network.. My guacamole docker is on a custom user defined network.. 

Edited February 4, 20206 yr by Chandler

Ok I think I have it working now. Removing the ports still left the port mappings and I changed my apacheguacamole letsencrypt config to point to the bridge IP address of letsencrypt and it seems to be working. 

I have a new question though.. apacheguacamole uses port 8080. I have another docker that also uses port 8080 by default. How do I change the default mapping to allow both of them to work? 

 

As an example:

 

Organizr uses the same internal ports as letsencrypt. So when I try to point towards organizr it goes to letsencrypt. I don't have any ports set up in the container so how can I change the default ones shown above? 

Edited February 4, 20206 yr by Chandler