I'm building this CLI as a side-project and a way to help on the usage with the main tool.
It's in a early version, then at the moment I'm trying to be as much as possible compatible with `docker-compose` config file, and in the current version we're supporting two commands: `up` and `down`.
> Any reason why don’t implement this as a plugin for the container CLI?
I did a different CLI because, considering that Apple released their v0.1.0, I'm not sure if they're working in some kind of official support for compose YAMLs.
With that in mind, I tried to avoid coupling it into the container CLI, to avoid injecting any kind of breaking change or something else which could cause any issue in the future.
On my current implementation, I didn't work with DNS/Network Resolution because I need to understand better what I can/can't do with the API Apple provides, so the only things it does is handling the port mapping using `socat`, as the docs recommends.
I know docker is easier to dev on for many currently, it's also been around longer, but there is a widening gap between docker deployments in production and podman deployments in production and it isn't nearly as smooth or secure as either should be.
yodon•7mo ago
Noghartt•7mo ago
figmert•7mo ago
WhyNotHugo•7mo ago
esseph•7mo ago
I hope there is something new. The tooling and deployment fragmentation is a nightmare.
From a security and open standards pov, we maybe should be moving to podman/OCI.
The docker tooling was often focused on the dev experience and it showed, but it wasn't a system with a good security model and this transition is a large part of that pain.