I just hit Docker Hub's asinine rate-limiting. Well, *I* didn't hit it, my Docker-container-registry-as-a-service hit it, sooooo. Great. Deploys of m.t are currently blocked.
I cannot *WAIT* to get off this for the instance.
Docker is such a cool concept but between technical hurdles and everybody trying to make a buck, it sucks. Sorry to say it but Docker sucks.
@ashfurrow There was some other container registry for Docker images. Maybe I should switch to that...
@Gargron I might use another registry for the Dockerfile if I keep running into problems, as a workaround for now. But it has to be a registry that I trust, which has implications.
I'm out of office next week – hoping to move m.t off of Docker then. Using it made sense in 2017 but I'm comfortable enough with systems administration now that I'm not getting much value from it anymore.
But their official recommendation is to mirror the base images from dockerhub and build things from there in your container images.
@ashfurrow I have been using gitlab which has integrated CI and docker registry in the free version. I had couple of repos that rebuild on commit and uploaded image to local registry.
@ashfurrow "Everyone trying to make a buck" is where it lost its way a lot, honestly. (A fact that is itself reflected in a whoooooole lot of commercialized corporate productized open source, tbh)
@stevestreza yeah. Ironically enough, Swift on Linux getting distributed in Docker containers was one of the more exciting use cases for me. Not anything devops.
We migrated most of our Docker images to our own internal gitlab instance for that very reason
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!