You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
podman promises to be better Docker, and provides pods on top of ordinary containers, similar to kubernetes. Let's see if it can handle the standard case of test driven/iterative infrastructure development.
In https://github.com/release-monitoring/anitya Dockerfile is greatly outdated. Missing dependencies, absent services, different commands that run for Dockerfile, for Development Ansible and for production.
Let's try to see how podman improves that. And first, let's setup DevOps workbench.
Terminal pane to write container build code
Terminal pane that watches container build code, rebuilds container and restarts it (could be two panes - one for building, one for starting)
Terminal pane that waits for container to startup, then for services to start, then testes them and report result
This is setup for TDD for infrastructure. The third panel is our test, which is connected to the second panel - if container failed to start or failed in the middle, the test panel should detect that and report as well.
Them we can just leave all three panels independently and work on the code.
The text was updated successfully, but these errors were encountered:
podman
promises to be better Docker, and providespods
on top of ordinary containers, similar tokubernetes
. Let's see if it can handle the standard case of test driven/iterative infrastructure development.In https://github.com/release-monitoring/anitya Dockerfile is greatly outdated. Missing dependencies, absent services, different commands that run for Dockerfile, for Development Ansible and for production.
Let's try to see how
podman
improves that. And first, let's setup DevOps workbench.This is setup for TDD for infrastructure. The third panel is our test, which is connected to the second panel - if container failed to start or failed in the middle, the test panel should detect that and report as well.
Them we can just leave all three panels independently and work on the code.
The text was updated successfully, but these errors were encountered: