Post · bonfire.cafe

Post

Joel Carnat ♑ 🤪

@joel@gts.tumfatig.net · 2 weeks ago

First notes about using #podman instead of #docker - yeah, I’m getting agile…

command line looks about the same (so far) and can run a few (standalone) images.
podman compose and podman-compose are two different things.
podman compose does not seem to be able to use a docker-compose file. podman-compose can but requires the docker daemon to be running. Which makes using podman useless IMHO.
passing container parameters on the CLI is way less convinient that using a YAML file as soon as you get more than a single expose port and volume.

Disclaimer: those notes are "AFAIK for the moment".

dch :flantifa: :flan_hacker:

@dch@bsd.network replied · 2 weeks ago

@joel similar experience here.

I think the biggest shift is when you can compose these containers together. I compare this to doing the same thing with terraform or ansible, and doing a rolling deploy, it’s a lot cleaner and simpler than before.

Building in containers and then running tests, on exactly the same artefact that I intend to deploy is pretty neat and tidy.

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.7 no JS en

Automatic federation enabled