podman-compose VS kaniko

Podman (via podman-compose),

Source code for the feature is here if you care to inspect it:

https://github.com/containers/podman-compose/blob/bce40c2db3...

Admittedly, I'm still on podman 4.3.1, but I dont' see any reason why this would stop working in later versions of podman.

Can someone link me to what Compose means in this context? Google takes me to https://github.com/containers/podman-compose but I just wanna make sure that's what they are talking about.

🛑 Docker Desktop is free for personal use but requires a paid subscription for enterprises. A free open source alternative is Podman and Podman Compose which uses the same core syntax as the Docker tools and can be used as a near drop-in replacement.

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

From googling this error I've come across a few different threads but I haven't gained any success. Firstly I found this github thread which doesn't reference my error but still seems related. I followed the "sudo podman-compose systemd --action create-unit" and "podman-compose systemd -a register -f myfile.yml" minus the -f flag as it wouldnt run with that. This indeed created a [email protected] file, but its created in the /etc/systemd/user directory rather than /etc/systemd/system which raises an issue as I'm having to run these two containers as root. I try registering the podman-compose@torrent but I'm told the service doesnt exist. Running it as user I'm told it failed to connect to bus: no medium found. So I basically reached a dead end there.

Have a look at Podman Compose

You can also use podman-compose for the orchestration https://github.com/containers/podman-compose

If all you need to do is build container, you can use https://github.com/GoogleContainerTools/kaniko

Kaniko for building the container images

kaniko

You should maybe look into Kaniko or use some other build tool

If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).

Check out Kaniko for building containers https://github.com/GoogleContainerTools/kaniko . Only issue is it doesnt support windows containers.

It took less than 5 minutes to install. It quickly analysed the repo and identified easy ways to make the project more secure. Priya Wadhwa, Kaniko

I'd suggest to take a look at the Kaniko project, combined with custom container images in Lambda functions.

kaniko is a tool that allows you to build container images inside Kubernetes without the need for the Docker daemon. Effectively, it allows you to build Docker images without docker build.

Kubernetes prefers to pull containers from registries. You may be able to work around it by specifying a local image in your Kube manifest. Both https://github.com/GoogleContainerTools/kaniko and/ or https://www.devspace.sh/ may help.