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

I took the time to learn quadlet and that replaced docker-compose (podman-compose) which is great, but what is hard and haven't understood is UID/GID mapping for podman. Like with root it seems to be as easy as docker but podman should be done rootless and the way to map without root is so hard. Crossing my fingers I can figure this out.

#Podman #DockerCompose #Docker #PodmanCompose #FOSS #Containers #Containerization #Linux

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

#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

podman - erste schritte -
#podman #podmancompose #container #fedoraserver #linuxgsm

https://log.wiuwiu.org/podman-teil-2

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.