#Overseerr through Docker not visible on network

7 messages · Page 1 of 1 (latest)

dim tartan
#

Hi all!

I installed Overseerr through docker on my Odroid N2+ running a fresh, updated installation of Arch linux; running with docker compose.

version: '3'

services:
  overseerr:
    image: sctx/overseerr:latest
    container_name: overseerr
    environment:
      - LOG_LEVEL=debug
      - TZ=America/Los_Angeles
      - PORT=5055 #optional
    ports:
      - 5055:5055
    volumes:
      - /mnt/external002/overseerr/config:/app/config
    restart: unless-stopped

docker ps looks reasonable to me

CONTAINER ID   IMAGE                   COMMAND                  CREATED          STATUS         PORTS                                       NAMES
eb8c95469bf1   sctx/overseerr:latest   "/sbin/tini -- yarn …"   21 minutes ago   Up 3 minutes   0.0.0.0:5055->5055/tcp, :::5055->5055/tcp   overseerr

I've tried accessing 192.168.1.219:5050 in the browser on my desktop on the same LAN, and by curling

➜  overseerr curl 192.168.1.219:5050
curl: (7) Failed to connect to 192.168.1.219 port 5050 after 0 ms: Couldn't connect to server
➜  overseerr curl localhost:5050
curl: (7) Failed to connect to localhost port 5050 after 0 ms: Couldn't connect to server
➜  overseerr curl 172.19.0.1:5050
curl: (7) Failed to connect to 172.19.0.1 port 5050 after 0 ms: Couldn't connect to server
➜  overseerr curl 172.19.0.2:5050
curl: (7) Failed to connect to 172.19.0.2 port 5050 after 0 ms: Couldn't connect to server

Overseer seems to be running because I can see the config files it created, but I can't seem to access it on the network. I am a bit of a docker noob but I would appreciate any help!

📎 ip_addr_output.txt
stiff stratus
#

firewall? try localhost as well, do you know what network the container is on?

#

bridge, host?

dim tartan
#

the curl commands were run on localhost

#

but its a headless machine

#

I believe it should be using bridge network