HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
spotify
docker-gc
Shell2015–2018
spotify / docker-gc · Archived

docker-gc

INACTIVE: Docker garbage collection of containers and images

Command LineSystems & InfrastructureCreative & MediaDevOps & Cloud
Explore on GitHubRead Hacker News discussions
6Distinct people
6Mentions
0Explicit recommenders
5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

INACTIVE: Docker garbage collection of containers and images

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2015-07-29 02:57:33 UTC to 2018-04-22 00:21:58 UTC.

01232015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC220
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101

What Hacker News says

6 sources
imauld·Apr 22, 2018
You can create a virtual networks and have all the related containers running on one of these networks. They can communicate directly to each other in the docker compose method (define a service `foo` and any container on that network can communicate with it like `http://foo/some/endpoint`) or have a some other message bus (redis, rabbitmq, zeromq, kafka whatever you want really) running on the docker network that the other containers use to communicate. Is this the best solution always? Probably not. An example of using a Docker container as an isolated system process would be Spotify's `docker-gc`. https://github.com/spotify/docker-gc
In Ask HN: What are the disadvantages of Docker?
awinder·Nov 4, 2016
"The only way to clean space is to run this hack, preferably in cron every day" https://github.com/spotify/docker-gc "Many attempts can be found on the internet, none of which works well. There is no API to list images with dates" http://portainer.io/ seems to be able to do it, docker images lists it... I mean, I don't want to call bullshit without knowing the full story, but... "So, the docker guys wrote a new filesystem, called overlay" https://github.com/torvalds/linux/commit/e9be9d5e76e34872f0c... written in 2014 by the linux kernal team / Linus, but OK cool story "It affects ALL systems on the planet configured with the docker repository" OK, this is why people use AWS' container repo, or they use the open source software and maintain their own repo... this happens with any of the public repo services, and it was 7 hours. "The regist
Read the rest
ry just grows forever" S3 is a supported backend, highly would advise anyone running their own repo to use it (or have a similar expanding-space story). There's also a config flag for the repo to allow removing images. Obviously wouldn't want to use this if you're hosting a public repo but internally, go for it, it's off by default, seems sane enough. "Erlang applications and containers don’t go along" I'm certain that people are running erlang containers successfully. "Docker is a dangerous liability that could put millions at risk. It is banned from all core systems." Daily FUD allowance exhausted. I guess the tone of this article really bugged me because there's obviously a point to be made from this experience that running Docker is more difficult & error prone than it should be. And maybe it wasn't a great fit for this company culture. But this article crossed the "we didn't have a good experience, therefore, it's BS software" line, and frankly, that attitude may very well have been to blame for the lack of success just as much as docker's shortcomings were...
In Docker in Production: A History of Failure

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.