Can't connect to Docker container running on Droplet

I’m trying to run a docker container via docker-compose on a droplet, but finding I’m not able at all to access the container from on the droplet (with curl). I followed this guide to install Docker, plus I added docker-compose.

Here’s what my docker-compose.yml looks like:

version: "2.1"
    container_name: sonarr
      - PUID=1000
      - PGID=132
      - TZ=Europe/London
      - ~/docker/configs/sonarr:/config
      - 8989:8989
    restart: unless-stopped

It starts up fine, if I open a shell on the container I can see the service is running and curl it with localhost:8989. But then from outside the container (on the droplet), curl localhost:8989 returns with ‘Connection reset by peer’

I’ve tried running this exact config on a local server also running Ubuntu 20.04 and it all works as expected, I can curl from outside the container and get the response from inside (although that’s running Docker v19 but I hope that wouldn’t affect it?). All I can conclude is it’s something to do with a firewall or iptables or something on the droplet? But I’m not trying to even access it externally, purely from on the droplet.

Any advice? Thanks!


Doing some more digging, I’ve realised that actually no networking is working from inside the container. If I open a shell in the container, even curl returns Could not resolve host and trying the IP of a website hangs forever. Again, these work fine in the identical container I’m running in a newly created droplet.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there @dwm,

I could suggest a couple of things:

  • Make sure that the Docker container is still listening on that port:
netstat -plant | grep 8989

If not, I would recommend checking your container logs to see what might have happened.

  • If you have a firewall like UFW, make sure to allow the port:
ufw allow 8989

Let me know how it goes! Regards, Bobby