3 ms·
I've always hated the docker model of the image namespace. It's like those cloud-based routers you can buy. Docker actively prevents you from having a private
by m463 2y ago
I've always hated the docker model of the image namespace. It's like those cloud-based routers you can buy.
Docker actively prevents you from having a private repo. They don't want you to point away from their cloud.
Redhat understood this and podman allows you to have a private docker infrastructure, disconnected from docker hub.
For my personal stuff, I would like to use "FROM scratch" and build my personal containers in my own ecosystem.
- Carrok 2y ago> Docker actively prevents you from having a private repo. In what ways? I use private repos daily with no issues.
- m463 2y agoIf you reference a container without a domain, you pull from docker.io With podman, you can control this with $HOME/.config/containers/registries.conf or /etc/containers/registries.conf with docker, not possible (though you can hack mirrors) https://stackoverflow.com/questions/33054369/how-to-change-the-default-docker-registry-from-docker-io-to-my-private-registry https://stackoverflow.com/questions/33054369/how-to-change-t...
- Carrok 2y agoSo.. just use a domain. This seems like a nothing burger.
- m463 2y agoNot all dockerfiles (especially multi-stage builds) are easily sanitized for this. think FROM python:latest or FROM ubuntu:20.04 AS build They've put deliberate barriers in the way of using docker commands without accessing their cloud.
- Cyph0n 2y agoOr even easier: just fully qualify all images. With Podman: nginx => docker.io/library/nginx linuxserver/plex => docker.io/linuxserver/plex
- icedchai 2y agoOne of the first things I did was set up a my own container registry with Docker. It's not terribly difficult.
- mountainriver 2y agoHuh? In what way does docker prevent you from having a private repo? Its a couple clicks to get on any cloud