@malcolmlewis1 your suggestion of podman generate kube … is not a viable long-term solution. Obviously, the information you weren’t aware of, as I’m currently just attempting to get things working with a much simpler implementation, but we utilize build scripts based on different scenario files that get loaded at launch time. Part of the process is to build the images for the containers that will be needed based on different parameters associated with the config files. Building, running, then generating a manifest file from a running container, and then running a new container within the cluster would not be practical.
That appears to be what you have suggested. correct?
@KianaClover No not yet. I’m still attempting to figure it out. I have had to switch focus to another program, but I jump back to this issue as often as I can.
@bpedersen2 Thank you. @malcolmlewis1 suggested a link for setting up a private repo. I’m going to attempt to look at that today.
just to clarify the steps you’re suggesting.
- Create a private registry
- build a Podman image, but tag the image so that includes details associated with the private register
- push the image to the private registry
- when generating the manifest files, it should pull the image from the private registry
correct? Through my research, I’m finding a lot of links that suggest Podman was not designed to be used within Kubernetes. I can’t remember what the article said exactly. actually here is a link to a post I quickly found, link here. Granted these posts are a few years old. I don’t understand it, but I’ve also found references that the runtime engine isn’t compatible with Podman. I haven’t spent any time looking at it, but something about using CRI-O vs. Containerd, and even Docker was mentioned at some point.
is what I’m attempting to do Possible? Or is it one of those things that have a few years of learning and experience you can hack it together to work?