Replies: 2 comments 1 reply
-
It looks like your volume mappings are incorrect.
should be
which is mapping your paths onto paths inside the docker container, so the software only sees |
Beta Was this translation helpful? Give feedback.
-
Hmm thank you but still no change for me docker container list |
Beta Was this translation helpful? Give feedback.
-
Trying to work with a docker image off my nas since running on a pi didn't seem to be a option (didn't want to put docker on the pi for a couple reasons). Anyway, the container claims to start but is not accessible via IP:PORT. I'm pretty new to docker though and there are lots I don't get about the syntax (argh always one more thing).
I have tried a couple different sheet variations: but this eems to start and stay running
docker pull advplyr/audiobookshelf
docker run -d
-e AUDIOBOOKSHELF_UID=99
-e AUDIOBOOKSHELF_GID=100
-p 13378:8080
-v /mnt/HD/HD_a2/Public/Audiobooks/audiobooks
-v /mnt/HD/HD_a2/Public/Audiobooks/config
-v /mnt/HD/HD_a2/Public/Audiobooks/meta
--name audiobookshelf
--rm advplyr/audiobookshelf
home # docker container list
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
35383bd415a5 advplyr/audiobookshelf "docker-entrypoint.s…" 18 seconds ago Up 7 seconds 80/tcp, 0.0.0.0:13378->8080/tcp audiobookshelf
home #
on trying to connect local ip:port
generic reply
This site can’t be reached xxx.xxx.xxx.xxx refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Beta Was this translation helpful? Give feedback.
All reactions