Lscr.io is down for me, anyone else?

I’m not able to pull or ping lscr.io from any of my devices. The status dashboard says everything is up but I cannot connect from any computer or network.

It doesn’t respond to pings, but it is up. Do you have an ad blocking thing? I would start there

I’ve disabled my dns blocklist and still nothing. No pings, pulling with docker gives me “manifest unknown”.

Are you pulling a manifest that exists…

calibre, calibre-web, radarr, sonarr all showed that message at one point or another.

You need to provide more details to get any help, unknown manifest is a clear indication you are reaching lscr but something else is wrong

Okay sorry I’m not even sure what would help. I’m inexperienced with docker. Would my docker-compose.yml file contents be the problem?

There is no way I can know that without you sharing it. Our readme has a tricks shooting section to get container logs, versions, etc . The compose at a minimum is good, you can share the output of uname -mr && docker version too

Here’s the compose scrubbed of sensitive info and shortened because I can’t post more than two links as a new user:

chenge@chenge-nas:~/temp_media_stack_test$ cat docker-compose.yml
services:

Gluetun (VPN Client)

gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun
cap_add:
- NET_ADMIN
ports:
- 8888:8888/tcp # HTTP proxy (optional)
- 8388:8388/udp # SOCKS5 proxy (optional)
# Add qBittorrent specific port if your VPN provides port forwarding
# - 6881:6881/tcp
# - 6881:6881/udp
environment:
- VPN_SERVICE_PROVIDER= # REQUIRED
- VPN_TYPE=openvpn # or wireguard
- VPN_USER= # REQUIRED
- VPN_PASSWORD= # REQUIRED
- TZ=America/New_York
# Add provider-specific variables (e.g., SERVER_COUNTRIES, PORT_FORWARDING=on, etc.)
volumes:
- /mnt/data/appdata/gluetun:/gluetun # Persistent configuration
restart: unless-stopped

Prowlarr - Indexer Manager

prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000 # Your user ID
- PGID=1000 # Your group ID
- TZ=America/New_York
volumes:
- /mnt/data/appdata/prowlarr:/config
restart: unless-stopped

qBittorrent - Torrent Client

qbittorrent:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbittorrent
network_mode: service:gluetun # CRUCIAL: Routes qBittorrent traffic through Gluetun
environment:
- PUID=1000 # Your user ID
- PGID=1000 # Your group ID
- TZ=America/New_York
- WEBUI_PORT=8080 # Internal Web UI port
volumes:
- /mnt/data/appdata/qbittorrent:/config
- /mnt/data/downloads:/downloads # Downloads remain on OS drive (NVMe)
- /mnt/data/downloads/incomplete:/downloads/incomplete # For incomplete downloads
ports:
- “8080:8080” # Keep for direct LAN access to WebUI, can be removed if only using NPM
restart: unless-stopped

And the uname output:
chenge@chenge-nas:~/temp_media_stack_test$ uname -mr && docker version
6.8.0-60-generic x86_64
Client: Docker Engine - Community
Version: 28.1.1
API version: 1.49
Go version: go1.23.8
Git commit: 4eba377
Built: Fri Apr 18 09:52:14 2025
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 28.1.1
API version: 1.49 (minimum version 1.24)
Go version: go1.23.8
Git commit: 01f442b
Built: Fri Apr 18 09:52:14 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
chenge@chenge-nas:~/temp_media_stack_test$

nothing jumped out at me, try taking a look through our frequently asked questions for lscr, though if you say it’s intermittent, it’s going to be something very difficult to diagnose.