docker image prune
this post was submitted on 16 Mar 2025
75 points (100.0% liked)
Selfhosted
44780 readers
461 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Goodbye stopped containers.
IIRC, a normal prune doesn't get rid of those, only the --all prune does that. The normal one only erases images that aren't associated with any container.
docker container prune for containers only also.
bro downloaded the mudroom closet and has a whole stack of jacketts
I believe Linux Server builds images every day for most of their containers, even though there has been no code changes.
If the code doesn't change, the resulting docker image will have the same hash, and a new image won't be created
https://github.com/jackett/jackett/releases
Jackett is literally just releasing a new version every day
Laughs in nix
Do you have Kinsing? I just dealt with it this past week.
Real question is, why Jackett instead of Prowlarr? 😄
If i remember correctly, jackett allows you to add trackers that prowlarr doesn't have natively. Then you add jackett to prowlarr to distribute to the rest of your containers.
Dunno, man. Its been working so far. I'll check out prowlarr, thanks
It's* been working
Yeah no worries - I discovered Prowlarr from that exact same comment years ago so jumped at the opportunity to post it here 😆
Prowlarr's "guide" for docker implementation is scary
Nah, man. Check this out: https://prowlarr.com/#downloads-v3-other
Neither option makes me feel confident.
I am a bit confused tbh 😅
The link you send links to docker projects, the link I sent is the second one of those. Seems pretty straightforward?
But to be fair, I have never used docker for any of this. In my nix config, it's literally just:
services.prowlarr.enable = true;
services.prowlarr.openFirewall = true;
There's not really anything you need to configure host-side. Prowlarr needs to be able to communicate with sonarr and radarr (same as jackett), but otherwise it's basically stateless.
You might be right. Last time I checked I was still a bit "green" with this. It's been two years and I think it makes more sense now 😉
The main issue is that for the prowler developers it seems like none of the docker options is ideal....
Tbh the whole arr suite is a headache to get working well...
Never had an issue. But I installed them all using my distro package manager, so no hassle with volumes and links.
I have them all running in a docker compose, that also has gluetun as the gateway.
It's a real basic compse file, but I can share it if you like.
Sure, why not? I'm setting up my new server, so no better time. Thanks
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
cap_add:
- NET_ADMIN
environment:
- DNS_ADDRESS=
- PUID=1000
- PGID=1000
- SERVER_CITIES=
- FIREWALL_VPN_INPUT_PORTS=
- TZ=Etc/UTC
# Provider readmes: https://github.com/qdm12/gluetun-wiki/tree/main/setup/providers
- VPN_SERVICE_PROVIDER=
#- VPN_TYPE=openvpn
#- OPENVPN_CUSTOM_CONFIG=/config/custom.conf
#- VPN_TYPE=wireguard
#- WIREGUARD_PRIVATE_KEY=
#- WIREGUARD_ADDRESSES=
ports:
- 6767:6767 # bazaar
- 7878:7878 # radaar
- 8118:8118 # privoxy
- 8191:8191 # flaresolverr
- 8787:8787 # readaar
- 8989:8989 # sonaar
- 9091:9091 # transmission
- 9696:9696 # prowlarr
# You can add an forwarded listening ports your VPN provider might have here as well.
volumes:
- /data/gluetun:/config
bazarr:
image: lscr.io/linuxserver/bazarr:latest
container_name: bazarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/bazarr:/config
- /share/downloads/movies:/share/downloads/movies
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
flaresolverr:
# DockerHub mirror flaresolverr/flaresolverr:latest
image: ghcr.io/flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- LOG_LEVEL=info
- LOG_HTML=false
- CAPTCHA_SOLVER=none
- TZ=Etc/UTC
restart: unless-stopped
network_mode: service:gluetun
privoxy:
image: caligari/privoxy:latest
container_name: privoxy
restart: unless-stopped
network_mode: service:gluetun
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/prowlarr:/config
restart: unless-stopped
network_mode: service:gluetun
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/radarr:/config
- /share/downloads/movies:/share/downloads/movies
restart: unless-stopped
network_mode: service:gluetun
readarr:
image: lscr.io/linuxserver/readarr:develop
container_name: readarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/readarr:/config
- /share/downloads/books:/share/downloads/books
restart: unless-stopped
network_mode: service:gluetun
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /data/sonarr:/config
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
transmission:
image: lscr.io/linuxserver/transmission:latest
container_name: transmission
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- TRANSMISSION_WEB_HOME= #optional
- USER= #optional
- PASS= #optional
- WHITELIST= #optional
- PEERPORT= #optional
- HOST_WHITELIST= #optional
volumes:
- /data/transmission:/config
- /share/downloads/movies:/share/downloads/movies
- /share/downloads/books:/share/downloads/books
- /share/downloads/tv:/share/downloads/tv
restart: unless-stopped
network_mode: service:gluetun
watchtower:
container_name: watchtower
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
network_mode: service:gluetun
You might also want to check out https://yams.media/, it's pretty much an install script and configuration walkthrough that's very complete and detailed. Includes most relevant Arrs and gluetun builtin. Containerized. Choice of Emby, Plex or Jellyfin.
Prowlarr, recyclarr, and trash guides.
I tried recyclearr but found configarr to be more flexible.
https://github.com/raydak-labs/configarr/
Here is my configarr config:https://github.com/raldone01/configarr_config
I believe configarr is just a superset of recyclearr.
it's those pesky docker volume maps and hardlinks
What’s not working for you?
For me after a decade using -arr the only thing I’ve had significant issues with has been trying to use the Tailscale integration on Unraid 7 to tunnel the dockers through an exit node which is… not at all the fault of -arr containers lol
I've had the opposite experience. It all "just worked". Try running unraid. It makes a lot of it so much easier.
load more comments
(9 replies)
Looking at linuxserver/jackett on Docker Hub, it seems it indeed update everyday.
load more comments
(4 replies)
Because you are pulling it every day.
Images only download when there's a new release, so you didn't answer the question.
The answer is: Because Jackett has daily releases. Maybe they don't version their releases.
Sure, but also, why are you pulling daily to begin with?
Because it's an automated system which looks for updates daily. Is that a serious question?
Yes, it's a serious question. Pulling far too often is exactly why Docker Hub is implementing lower daily limits.
You're suggesting that a single daily image pull is somehow abusive and the cause for Docker Hub imposing limits. This argument is invalid because even after Docker Hub imposes it's limits, pulling an image daily is well within those limits.
However, I am of the opinion that Portainer shouldn't be downloading images unless the container is being deployed, if that's actually what's happening, we don't know.
OP is doing nothing wrong, so please refrain from making illogical bad faith arguments.