diskdiddler
Wizard
- Joined
- Jul 9, 2014
- Messages
- 2,377
EDIT:
This has been reported by me as a bug, the --net=host is the only way, to get ports, to present over docker externally.
-p <portoutside>:<portinside> does not appear to be working, how I would expect it to work on a docker host.
Original post:
Hello!
Disclaimer: unsupported, I'm just using the CLI to run docker containers, I'm not using the webUI and all the k8 stuff.
I have installed fresh on a spare machine.
Created an SSD based pool.
I have clicked on apps and successfully configured the SSDPOOL to be the app directory for apps.
I have run sudo docker pull xyz:abc and managed to pull several containers.
These are listed in the webui under manage docker images
Some of them even run fine....
I am curious if somehow some ports are blocked or something simple?
Example these 2 work fine:
However these 3 do not work.
I can clearly see, that data is written to /mnt/SSDPOOL/dockerdata/medua or /mnt/SSDPOOL/dockerdata/speedtest-tracker & /mnt/SSDPOOL/dockerdata/jdownloader:/config
I can sudo docker exec -i <containername> /bin/bash and navigate, I can even mkdir -v mounted folders and write contents out to the real filesystem.
None the less there's nothing coming up on :8765 :8111 or :5800
?
Has anyone else encountered this, am I doing something foolish or is there some kind of linux firewall / ip blocking against certain ports? I'm not entirely sure.
Obviously, I can't run anything natively, on port 80 but this is not that port.
Any tips?
This has been reported by me as a bug, the --net=host is the only way, to get ports, to present over docker externally.
-p <portoutside>:<portinside> does not appear to be working, how I would expect it to work on a docker host.
Original post:
Hello!
Disclaimer: unsupported, I'm just using the CLI to run docker containers, I'm not using the webUI and all the k8 stuff.
I have installed fresh on a spare machine.
Created an SSD based pool.
I have clicked on apps and successfully configured the SSDPOOL to be the app directory for apps.
I have run sudo docker pull xyz:abc and managed to pull several containers.
These are listed in the webui under manage docker images
Some of them even run fine....
I am curious if somehow some ports are blocked or something simple?
Example these 2 work fine:
sudo docker run -d --name=couchpotato -e PUID=0 -e PGID=0 -e TZ=Australia/Melbourne -e UMASK_SET=022 --net=host -p 5050:5050 -v /mnt/SSDPOOL/dockerdata/couchpotato:/config --restart unless-stopped linuxserver/couchpotato
sudo docker run -d --name=qbittorrent --net=host -e PUID=0 -e PGID=0 -e TZ=Australia/Melbourne -e UMASK_SET=022 -e WEBUI_PORT=8080 -p 6881:6881 -p 6881:6881/udp -p 8080:8080 -v /mnt/SSDPOOL/dockerdata/qbittorrent/:/config --restart unless-stopped linuxserver/qbittorrent
However these 3 do not work.
sudo docker run -d --name=jdownloader-2 -p 5800:5800 -p 3129:3129 -e USER_ID=0 -e GROUP_ID=0 -e UMASK=000 -e DISPLAY_WIDTH=1520 -e DISPLAY_HEIGHT=620 -v /mnt/SSDPOOL/dockerdata/jdownloader:/config:rw -v /etc/localtime:/etc/localtime --restart=unless-stopped jlesage/jdownloader-2
sudo docker run -d --name=speedtest-tracker -p 8765:80 -v /mnt/SSDPOOL/dockerdata/speedtest-tracker/:/config -e TZ=Australia/Melbourne -e OOKLA_EULA_GDPR=true --restart unless-stopped henrywhitaker3/speedtest-tracker:dev
sudo docker run -d --name=medusa --dns=192.168.0.252 --restart unless-stopped -v /mnt/SSDPOOL/dockerdata/medusa:/config -e PUID=0 -e PGID=0 -e TZ=Australia/Melbourne -p 8111:8081 pymedusa/medusa
I can clearly see, that data is written to /mnt/SSDPOOL/dockerdata/medua or /mnt/SSDPOOL/dockerdata/speedtest-tracker & /mnt/SSDPOOL/dockerdata/jdownloader:/config
I can sudo docker exec -i <containername> /bin/bash and navigate, I can even mkdir -v mounted folders and write contents out to the real filesystem.
None the less there's nothing coming up on :8765 :8111 or :5800
?
Has anyone else encountered this, am I doing something foolish or is there some kind of linux firewall / ip blocking against certain ports? I'm not entirely sure.
Obviously, I can't run anything natively, on port 80 but this is not that port.
Any tips?
Last edited: