191–200 of 212 posts
Earlier quoted context omitted.
So is Podman, if you are to believe Red Hat's marketing on it.
I actually use Podman and write Kube config yaml instead of docker compose yaml. I do like it better. It's a bit more polished.
Earlier quoted context omitted.
Thank it looks great ! and yes, I believe it is the policy of linuxserver.io not to test or support officially podman. I have been trusting the plan but I notice that after 10 years of container industry standard etc. we have to search for podman friendly images to enjoy integration with the common Linux service manager... Now if container-based Linux distributions are the future I'm starting to wonder if we are not…
Fun fact, OpenSUSE actually already does that for some common server software (LDAP, dovecot, etc); they're quadlet/systemd unit files packaged up as RPMs though, I don't think they actually include the container image.
Earlier quoted context omitted.
If you want to really simplify using containers, you could just use systemd-nspawn.
Depends what you mean by simplifying. Does it have registries and the ecosystem of OCI containers? The killer feature of podman for me is that it works with docker which like or not most people are using. But I'll look into nspawn could be useful.
Not at all. If you want all that, docker/podman is better.
But if ultimate simplicity is your goal, it's worth looking into. They are -very- lightweight and fast by comparison.
Earlier quoted context omitted.
Lolol have been running compose in dev & prod for 7 years - still the best tool around.
That might work for whatever you are doing, but the truth is that root-ful containers are not appropriate for a lot of applications, and docker as a layer to your container runtime is rough sometimes. I don't think docker wants to continue to develop this anyway - they have had enough problems trying to be profitable so instead it is time to focus on docker desktop and charging for docker hub image hosting. I feel li…
It's quite unfortunate that this article mixes up what's necessary for podman quadlets with coreOS concepts. With quadlets, the only thing required is to drop a `.container` file in the right place and you end up with a container properly supervised by `systemd`. And this of course also supports per-user rootless containers as described in [1]. [1]: https://www.redhat.com/sysadmin/quadlet-podman
Earlier quoted context omitted.
because inin files have no or very limited support for nesting there are also some issues with keys being all string by default making some things like linting harder and allowing more less standard ways to get something done, e.g. in json true is true in init files all of true, 1, yes, y and others might be true depending on the application (but then yaml no problem is worse) also there is no clear single standard f…
you might want to read this fine piece of propaganda https://github.com/madmurphy/libconfini/wiki/An-INI-critique...
I'm really not sure.
I mean some of the critique is very reasonable like inline tables needing to be inline but inline arrays do not.
But then they present something as INI file which most INI parser will not parse and is directly against much of their previous critique.
and why do I have the feeling that the author is constantly screaming for help internally while writing this article?
Earlier quoted context omitted.
systemd is extremely intrusive. anything dependent on it is a failure.
By my calculations, considering much of the world runs on RH/Ubuntu/Debian, all of which use systemd, things depending on systemd are far from being a failure, cos they'll run on the majority of systems.
I started using quadlets for new system designs a month ago and I feel like I'm neck deep in it now. My conclusion is that there is absolutely no reason to stop using docker-compose if your developers are comfortable running one command, on one file, in one git root. Quadlets are basically docker compose, in systemd. They've finally done it, systemd has it all and now it even has docker compose. ;) That's really all…
Systemd had dependencies between services and containers since forever.
The only difference here seems to be podman instead of systemd-nspawn.
To me, this big problem with Docker is that it does a ton of changes to my system, even when I don't use it. It runs a daemon, it uses a bunch of IPs, it mounts a ton of stuff ... Is there a reason for all that noise and complexity? There can't be a reason until I run a container, right? And even then, it seems way too much. Is it different when using Quadlets?
No. It's just Docker being shit.