Problem mounting file following docker-compose guide

ℹ️ Support
21

Iit was in my old configuration, the one that worked

I just did a test by adding the port 80:8080 directive to my docker-compose.yml file and the port 8080 is well tuned

root@cassiopea:~/nc-docker # netstat -tulpen | grep 8080
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      0          2969150    296527/docker-proxy
tcp6       0      0 :::8080                 :::*                    LISTEN      0          2967927    296534/docker-proxy

The fact of having two containers listening both on port 80 is not disturbing?

nextcloud:28                     "/var/www/html/custo…"   8 minutes ago   Up 8 minutes             80/tcp                                  c4rter-notify_push-1
nextcloud:28                     "/cron.sh"               8 minutes ago   Up 8 minutes             80/tcp                                  c4rter-cron-1
22

Hi Willi,

I spent the day putting back my old docker config and you will see that it works (except https for now). I can access to NC too via local ip 192.168.1.48:8080

root@cassiopea:~/ncdoc #
root@cassiopea:~/ncdoc # lsof -i -P -n | grep LISTEN | grep docker
docker-pr 409409            root    4u  IPv4 3515691      0t0  TCP *:443 (LISTEN)
docker-pr 409416            root    4u  IPv6 3513779      0t0  TCP *:443 (LISTEN)
docker-pr 409429            root    4u  IPv4 3513110      0t0  TCP *:80 (LISTEN)
docker-pr 409435            root    4u  IPv6 3513795      0t0  TCP *:80 (LISTEN)
docker-pr 410454            root    4u  IPv4 3517745      0t0  TCP *:8080 (LISTEN)
docker-pr 410461            root    4u  IPv6 3519616      0t0  TCP *:8080 (LISTEN)

So we can rule out a block on my system side and focus on the network part of your script. If it can help you I based on the following tutorial

23

you can not mix and match different tutorials… and sometime even valid knowledge like checking for active ports doesn’t help. your old installation is very different in terms of networking:

this where “my guide” is using “proxy” (likely some traefik parts don’t match as well)…

and the most important difference:

while I’m using “expose” which doesn’t publish container ports on the host - this is the reason why you don’t see any open ports on the host while my setup is running - the only way to connect to the system is through the reverse proxy (network).

All this small pieces are not hard by itself but the combination requires some level of understanding and training if you willing to learn. I admit my guide is built after long studying, optimization and tuning. it is build using some advanced techniques to improve security, stability and supportability of the system and the result is different from what you see in other places - please take a time to understand it.