![]() So I guess I’m not working to quickly provision containerized work environments, as much as I am setting up the infrastructure to have them pre-built, and instantiated later, as needed… Then when I start to work, I can “throw away” a build environment and just jump into the latest one built and deployed to the registry. That way, whenever I change a config, Jenkings can automatically rebuild the chain of images (I’m trying to layer them), test them (maybe?), and then push the images to a registry. ![]() The goal, is ultimately to define build scripts in a repo, and then set it up with Jenkins or some other CI/CD system. I can then simply pull these images down and run them with podman, whenever I want. Using the scripts, I can build container images which define my work environments. It turns out buildah is very powerful and should provide a bunch of flexibility. I started to define my work environments in Dockerfiles, but decided to switch over to writing buildah. ![]() I’ve used ansible to provision my host systems in the past.įor the container side, I’m still in the planning/experimenting stages but I think I have an idea of what I plan to do.
0 Comments
Leave a Reply. |