Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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"
services:
sonarr:
image: ghcr.io/linuxserver/sonarr
container_name: sonarr
environment:
- PUID=1000
- PGID=132
- TZ=Europe/London
volumes:
- ~/docker/configs/sonarr:/config
ports:
- 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!
lwmeozrcbh
d1dd3d9538cc4d06b53e6d1d338d3f
50ff4e4b3c6c4999a12403b1ecda95
a6309a057c3f4cb38fb2e7feb67236
72e571841e7f4a6881090a2f3e93c0
7ce6bf277bff4d429ba493dd750e35
57a72a98162f46a5a5cd04d9b
Thomas Brocken
11575c6d695643cdb40ad47d0f1aea
tez.saad