Regarding your statement “let’s say that you
docker run -d -p 8080:8080 pydio/cells on your machine, then you will only be able to access to it through
https://localhost:8080 on the same machine that has the container running ( because of the external )”
The above is not true. The command represented above does not bind the container to the loopback device but rather to all interfaces and thus is accessible from any machine that is able to access the docker host/IP.
I have followed the modified instructions on docker hub which corresponds somewhat to the instructions above but I’m receiving the error that I initially started this post with. The instruction on docker hub state:
CELLS_BIND : address where the application http server is bound to. It MUST contain a server name and a port.
CELLS_EXTERNAL : url the end user will use to connect to the application.
If you want your application to run on the localhost at port 8080 and use the url mycells.mypydio.com, then set CELLS_BIND to localhost:8080 and CELLS_EXTERNAL to mycells.mypydio.com"
I have modified the relevant environment variables that are of concern in this post to be:
where “URL” is an internal url.
I have also tried adding the port to the end of CELLS_EXTERNAL, e.g. CELLS_EXTERNAL=URL:8080
but that does not work either.
Can you please provide a real working example that has been tested so that I can replicate on my machine without issue? It’s fine if the url is different but the instruction on docker hub and the instructions above do not work. Has the example on docker hub been tested? Are there any dependency settings that are excluded from the example behind the default, e.g. the hosts file?