Hier werden die Unterschiede zwischen zwei Versionen gezeigt.
| Beide Seiten, vorherige Überarbeitung Vorherige Überarbeitung Nächste Überarbeitung | Vorherige Überarbeitung | ||
|
admin_grundlagen:docker:installation [2026/05/22 18:17] ingo_wichmann [Rocky Linux (9)] |
admin_grundlagen:docker:installation [2026/06/01 08:08] (aktuell) ingo_wichmann [lokalen Proxy / Cache verwenden] |
||
|---|---|---|---|
| Zeile 37: | Zeile 37: | ||
| -> ''CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES'' | -> ''CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES'' | ||
| + | ++++ podman | | ||
| + | Podman benötigt keinen daemon. Aber es gibt einen Socket: | ||
| + | systemctl status podman.socket | ||
| + | ++++ | ||
| ====== Nutzer zur Gruppe docker hinzufügen ====== | ====== Nutzer zur Gruppe docker hinzufügen ====== | ||
| - | Erspart das ''sudo'' vor jedem ''docker''. Gibt dem Benutzer auf indirekt root-Rechte. | + | Erspart das ''sudo'' vor jedem ''docker''. Gibt dem Benutzer indirekt root-Rechte. |
| gpasswd -a nutzer43 docker | gpasswd -a nutzer43 docker | ||
| ====== lokalen Proxy / Cache verwenden ====== | ====== lokalen Proxy / Cache verwenden ====== | ||
| + | ++++ podman | | ||
| + | <file toml /etc/containers/registries.conf.d/10-local-docker-io-proxy.conf> | ||
| + | [[registry]] | ||
| + | prefix = "docker.io" | ||
| + | location = "docker-registry.guest.linuxhotel.de" | ||
| + | insecure = true | ||
| + | </file> | ||
| + | Testen, ob Images wirklich vom lokale Proxy geladen werden: | ||
| + | podman info --format json | jq '.registries."docker.io"' | ||
| + | (( alternativ: | ||
| + | podman info --format '{{(index .Registries "docker.io").Location}}' | ||
| + | )) | ||
| + | podman image rm ubuntu | ||
| + | podman pull --log-level=debug ubuntu | ||
| + | ++++ | ||
| + | |||
| <file json /etc/docker/daemon.json> | <file json /etc/docker/daemon.json> | ||
| { | { | ||
| Zeile 48: | Zeile 68: | ||
| } | } | ||
| </file> | </file> | ||
| + | |||
| + | Cloud VM: | ||
| + | |||
| + | <file json /etc/docker/daemon.json> | ||
| + | { | ||
| + | "registry-mirrors": ["https://registry.lab.linuxhotel.de/nb72bnerqxlnfahdeqsfzhwjjyiqmsoz"] | ||
| + | } | ||
| + | </file> | ||
| + | |||
| + | systemctl restart docker.service | ||
| + | |||
| + | ===== Prüfen, ob tatsächlich der Proxy verwendet wird: ===== | ||
| + | docker image rm ubuntu | ||
| + | docker image pull ubuntu | ||
| + | |||
| + | journalctl -eu docker | ||
| + | |||
| ====== Logs zu Systemd-Journald umleiten ====== | ====== Logs zu Systemd-Journald umleiten ====== | ||
| Zeile 54: | Zeile 91: | ||
| -> ''json-file'' (( "By default, no log-rotation is performed. As a result, log-files stored by the default json-file logging driver can cause a significant amount of disk space to be used for containers that generate much output, which can lead to disk space exhaustion. | -> ''json-file'' (( "By default, no log-rotation is performed. As a result, log-files stored by the default json-file logging driver can cause a significant amount of disk space to be used for containers that generate much output, which can lead to disk space exhaustion. | ||
| Docker keeps the json-file logging driver (without log-rotation) as a default to remain backwards compatible with older versions of Docker, and for situations where Docker is used as runtime for Kubernetes." https://docs.docker.com/engine/logging/configure/ )) | Docker keeps the json-file logging driver (without log-rotation) as a default to remain backwards compatible with older versions of Docker, and for situations where Docker is used as runtime for Kubernetes." https://docs.docker.com/engine/logging/configure/ )) | ||
| + | |||
| + | ++++ podman | | ||
| + | podman info --format '{{.Host.LogDriver}}' | ||
| + | -> ''journald'' ist default | ||
| + | ++++ | ||
| Container starten, der viele Logmeldungen produziert: | Container starten, der viele Logmeldungen produziert: | ||