#podmancompose — Public Fediverse posts

Episode 7 of the DevOps Tools Engineer 2.0 Introduction series dives into exam objective #ContainerOrchestration.

Learn how #DockerCompose & #PodmanCompose define and run multi-container applications for modern #DevOps workflows: https://lpi.org/gfrl

#DevOps #containerorchestration #dockercompose #podmancompose #microservices #services #networks

Episode 7 of the DevOps Tools Engineer 2.0 Introduction series dives into exam objective #ContainerOrchestration.

Learn how #DockerCompose & #PodmanCompose define and run multi-container applications for modern #DevOps workflows: https://lpi.org/gfrl

#DevOps #containerorchestration #dockercompose #podmancompose #microservices #services #networks

Episode 7 of the DevOps Tools Engineer 2.0 Introduction series dives into exam objective #ContainerOrchestration.

Learn how #DockerCompose & #PodmanCompose define and run multi-container applications for modern #DevOps workflows: https://lpi.org/gfrl

#DevOps #containerorchestration #dockercompose #podmancompose #microservices #services #networks

Episode 7 of the DevOps Tools Engineer 2.0 Introduction series dives into exam objective #ContainerOrchestration.

Learn how #DockerCompose & #PodmanCompose define and run multi-container applications for modern #DevOps workflows: https://lpi.org/gfrl

#DevOps #containerorchestration #dockercompose #podmancompose #microservices #services #networks

Episode 7 of the DevOps Tools Engineer 2.0 Introduction series dives into exam objective #ContainerOrchestration.

Learn how #DockerCompose & #PodmanCompose define and run multi-container applications for modern #DevOps workflows: https://lpi.org/gfrl

#DevOps #containerorchestration #dockercompose #podmancompose #microservices #services #networks

Ignore my bitching about #podmancompose

Turns out, I was using version 1.0.buggy
vs the latest 1.5.notbuggy

/eyeroll #podman

Yeah... so #Podman is defo not ready for show time.

"Rootless containers unable to be assigned static IP addresses" (I need it because the NginX address resolver takes too long... intermittent 502 reasons)

https://github.com/containers/podman/issues/7842 (Bug reported 2020!)

I am beginning to suspect folks who are enthusiastic about #Podman are enthusiastic about the CONCEPT of Podman, not its production suitability.

#podmancompose always seems to be the showstopper.

I have invested a lot of time into Podman... but I may need to go back to #Docker and just screw down the containers to minimse #sploits

Yeah... so #Podman is defo not ready for show time.

"Rootless containers unable to be assigned static IP addresses" (I need it because the NginX address resolver takes too long... intermittent 502 reasons)

https://github.com/containers/podman/issues/7842 (Bug reported 2020!)

I am beginning to suspect folks who are enthusiastic about #Podman are enthusiastic about the CONCEPT of Podman, not its production suitability.

#podmancompose always seems to be the showstopper.

I have invested a lot of time into Podman... but I may need to go back to #Docker and just screw down the containers to minimse #sploits

Yeah... so #Podman is defo not ready for show time.

"Rootless containers unable to be assigned static IP addresses" (I need it because the NginX address resolver takes too long... intermittent 502 reasons)

https://github.com/containers/podman/issues/7842 (Bug reported 2020!)

I am beginning to suspect folks who are enthusiastic about #Podman are enthusiastic about the CONCEPT of Podman, not its production suitability.

#podmancompose always seems to be the showstopper.

I have invested a lot of time into Podman... but I may need to go back to #Docker and just screw down the containers to minimse #sploits

So yeaaah....
#podman
#podmancompose is DEFINITELY NOT ready for showtime...

#til podman lepiej wspiera pliki kubernetes niż pliki docker compose. I super, bo właśnie korzystam z niego do testowania, a środowisko produkcyjne mam na k8s, czyli nie muszę mieć oddzielnego pliku dla compose

#podman #podmanCompose #docker #dockerCompose #k8s #kubernetes

I have spent much of my Sunday speedrunning the documentation for #docker, #podman, #podmancompose and #finch and I am mad about it.

I'm also mad about how the entire ecosystem feels linearly fractured between "here, built and run a container, so flexible and dynamic" and "Describe your needs in excruciating detail. Include these 18 options we refuse to document adequately or perish. No, we won't be giving you any semantic or cli sugar to make things more securable. Fuck you; hire an Ops Team".

I know I'm no #devops expert; but when _every_ option causes that vague "Ur doin it rong" tension, it begins to feel like the problem is at least partially bad #documentation and partially paradigmical ossification.

Oh and #k8s can fuck right off; I'm hosting some software not launching a moon into another galaxy using only breakfast cereal and cotton gins.

In meinem Fall war das eindeutig selbstverschuldet und noch nicht mal kaputt, aber halt nicht das, was ich erreichen wollte.

Ich wollte auf 28.0.5, aber in der #podman-compose war ':latest' definiert und vor zwei Tagen kam 29.0.0 raus, also wurde erfolgreich auf die neue Version migriert. Nur will ich die (jetzt noch) nicht und es gibt scheinbar keinen einfachen Weg zurück, weil #Nextcloud nicht abwärtskompatibel ist.

Dann teste ich jetzt mal das #Restore mit #restic...

Anyone running #PaperlessNGX #rootless using #Podman and #PodmanCompose under #Debian12? The volumes I'm mapping to the host always get chowned to 100999:100999, and that's with USERMAP_UID=1000 and USERMAP_GID=1000 in docker-compose.env.

Playing around with PODMAN_USERNS mainly leads to the container not starting at all (in at least one case because it can't install packages).

#paperless_ngx

Nun gut - der Schritt von #docker zu #podman ist getan und Dank #podman-compose läuft unsere #Nextcloud quasi 1:1 seit 8 Monaten stabil.

Es wird Zeit, den zweiten Schritt zu tun: Den Compose-Rotz in einen #Pod zu migrieren, um dann rootless Port 80 und 443 anzubieten und einfache #systemd - Integration in einem Rutsch zu erhalten.

Hab' ja noch keinen Schimmer, wie ich vorgehen soll...

I accept the fragmentation. Posting #podman #podmancompose, #guix stuff to Twitter was so foolish because where are the #foss folks? They're here.

Mit heute ist jetzt jedes von mir direkt genutzte Gerät #Docker frei.

Kein Docker, Docker-Compose, Docker-Maschine mehr. Nur noch #Podman und #podmancompose

👀 at you my little remaining servers

@Aarkon nicht mit #rocketchat aber mit #docker und #raspberrypi im allgemeinen.

Privat betreibe ich ein #FedoraIoT OS mit #podman (docker Alternative), #podmancompose (pendant zu docker) und #traefik als docker native proxy.

Was willst du denn wissen?

In jedem Fall wirst du ein arm / raspberry Pi kompatibles Image brauchen. Der Rest funktioniert dann nach Doku.

Schau dir zum Beispiel mal das folgende Docker hub Image an, das ist recht aktuell.

https://hub.docker.com/r/webhippie/rocketchat