toad.social

Linux MagazineICYMI: <a href="https://opensocial.at/profile/linuxnews" class="u-url mention" rel="nofollow noopener" target="_blank">@linuxnews</a> shows you how to install a containerized Linux distribution with Distrobox <a href="https://www.linux-magazine.com/Issues/2025/295/Distrobox?utm_source=mlm" rel="nofollow noopener" translate="no" target="_blank">https://www.linux-magazine.com/Issues/2025/295/Distrobox?utm_source=mlm</a> <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://fosstodon.org/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> <a href="https://fosstodon.org/tags/Lilipod" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lilipod</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#containers</a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://fosstodon.org/tags/Distrobox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Distrobox</a> <a href="https://fosstodon.org/tags/hypervisor" class="mention hashtag" rel="nofollow noopener" target="_blank">#hypervisor</a>

ede@kakam:~#Suche ein <a href="https://chaos.social/tags/Job" class="mention hashtag" rel="nofollow noopener" target="_blank">#Job</a> wo ich Linux administrieren darf. Habe den <a href="https://chaos.social/tags/LPIC1" class="mention hashtag" rel="nofollow noopener" target="_blank">#LPIC1</a>. Will als nächsten den <a href="https://chaos.social/tags/LPIC2" class="mention hashtag" rel="nofollow noopener" target="_blank">#LPIC2</a> machen. Tue Ding mit <a href="https://chaos.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>, <a href="https://chaos.social/tags/nixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#nixOS</a> und andern <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> Distros. Bin im Layer1-4 zu Hause und würde mich gern zum <a href="https://chaos.social/tags/DevOp" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOp</a> weiter entwickeln. Container und Virtualisierung sind kein Problem. Habe jahrelang mit <a href="https://chaos.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> und <a href="https://chaos.social/tags/vmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#vmware</a> rumgespielt. Auch <a href="https://chaos.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> und <a href="https://chaos.social/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> sind nicht unbekannt für mich. Hat jemand ne Idee oder ein Vorschlag?

Leon CowlePlayed around with <a href="https://hachyderm.io/tags/Fastly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fastly</a>'s new <a href="https://hachyderm.io/tags/MCP" class="mention hashtag" rel="nofollow noopener" target="_blank">#MCP</a> Server over the last few days (<a href="https://github.com/fastly/mcp" rel="nofollow noopener" translate="no" target="_blank">https://github.com/fastly/mcp</a>). Really cool interactions! (/cc <a href="https://mastodon.social/@fastlydevs" class="u-url mention" rel="nofollow noopener" target="_blank">@fastlydevs</a>)I did find that trying to download a certain part of our Fastly content (a large VCL file), it was truncated, and that's because the Fastly MCP server has a hard limit of 50kb in responses.So... I wrote my own little (very basic) MCP Server (I'm not a "programmer", but I like to tinker in Python) — only providing "initialize", "tools/list", and "tools/call", and one tool.I integrated it into first <a href="https://hachyderm.io/tags/claudecode" class="mention hashtag" rel="nofollow noopener" target="_blank">#claudecode</a> and then <a href="https://hachyderm.io/tags/gemini" class="mention hashtag" rel="nofollow noopener" target="_blank">#gemini</a> (both running inside <a href="https://hachyderm.io/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> containers) and soon had 2 working MCP servers configured into the AI assistants.Now I can download our VCL files at will, and have the AI assistants read them, in full, from disk, and go from there!That was fun!

Max ResingAnyone ever decided to run their own container registry? I am playing with the idea, but all I can find is how people deploy the <a href="https://hub.docker.com/_/registry/" rel="nofollow noopener" target="_blank">official docker registry</a>. Are there no alternatives to it?<a href="https://infosec.exchange/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://infosec.exchange/tags/registry" class="mention hashtag" rel="nofollow noopener" target="_blank">#registry</a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> <a href="https://infosec.exchange/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://infosec.exchange/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://infosec.exchange/tags/askmastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#askmastodon</a>

Andre HofmeisterDoes anyone know why JsonContent sometimes throws an IOException when it is used as HTTP request content, while creating a StringContent from JSON serialization does not?I understand the difference, and that the second one creates the JSON content ahead, but I do not understand why JsonContent causes an IOException (connection reset by peer): <a href="https://github.com/testcontainers/Docker.DotNet/pull/33" rel="nofollow noopener" translate="no" target="_blank">https://github.com/testcontainers/Docker.DotNet/pull/33</a>. <a href="https://mastodon.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://mastodon.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://mastodon.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a>

Bo MorganWoot. Successfully set up a svelte vite server within a podman container along with an nginx reverse proxy running in another podman container. It's all certbot https, including websockets. That's a good goal accomplished. Still need the REST API and database containers, but getting closer to containerizing my first web app.<a href="https://kolektiva.social/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://kolektiva.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://kolektiva.social/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#svelte</a> <a href="https://kolektiva.social/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://kolektiva.social/tags/vite" class="mention hashtag" rel="nofollow noopener" target="_blank">#vite</a> <a href="https://kolektiva.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://kolektiva.social/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapp</a>

WulfyIf you are using NPM (<a href="https://infosec.exchange/tags/NginX" class="mention hashtag" rel="nofollow noopener" target="_blank">#NginX</a> proxy Manager container) you may be getting 502 Gateway errors from Resty.There is a whole shopping list why it does not work...But what I found works for me is replacing the container name with the internal Docker IP address.Will probably fail when the stack is restarted... so better not restart 0_oI was trying the NPM container because its got a nice GUI and allows Advanced NginX configurations.My previous NginX container was <a href="https://infosec.exchange/tags/SteveLTN" class="mention hashtag" rel="nofollow noopener" target="_blank">#SteveLTN</a> /https-portal which was pretty robust and flexible. But no GUI and no Advanced configs (not that I could get them working anyway).Havnt tried <a href="https://infosec.exchange/tags/traefik" class="mention hashtag" rel="nofollow noopener" target="_blank">#traefik</a> yet. But it seems every proxy has its own weirdness.<a href="https://infosec.exchange/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://infosec.exchange/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a>

The Linux LighthouseWhy openSUSE MicroOS is the Best Immutable Linux Distro<a href="https://www.youtube.com/watch?v=mFpsbmbAN8I" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=mFpsbmbAN8I</a><a href="https://mastodon.social/tags/opensuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensuse</a> <a href="https://mastodon.social/tags/opensuseleap" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensuseleap</a> <a href="https://mastodon.social/tags/opensusetumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensusetumbleweed</a> <a href="https://mastodon.social/tags/leap" class="mention hashtag" rel="nofollow noopener" target="_blank">#leap</a> <a href="https://mastodon.social/tags/tumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#tumbleweed</a> <a href="https://mastodon.social/tags/slowroll" class="mention hashtag" rel="nofollow noopener" target="_blank">#slowroll</a> <a href="https://mastodon.social/tags/aeon" class="mention hashtag" rel="nofollow noopener" target="_blank">#aeon</a> <a href="https://mastodon.social/tags/leapmicro" class="mention hashtag" rel="nofollow noopener" target="_blank">#leapmicro</a> <a href="https://mastodon.social/tags/suse" class="mention hashtag" rel="nofollow noopener" target="_blank">#suse</a> <a href="https://mastodon.social/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/MicroOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicroOS</a> <a href="https://mastodon.social/tags/ImmutableLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImmutableLinux</a> <a href="https://mastodon.social/tags/LinuxForContainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxForContainers</a> <a href="https://mastodon.social/tags/LinuxServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxServer</a> <a href="https://mastodon.social/tags/LinuxDistro" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxDistro</a> <a href="https://mastodon.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://mastodon.social/tags/Flatpak" class="mention hashtag" rel="nofollow noopener" target="_blank">#Flatpak</a> <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> <a href="https://mastodon.social/tags/openSUSEMicroOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSEMicroOS</a> <a href="https://mastodon.social/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tumbleweed</a> <a href="https://mastodon.social/tags/LinuxAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxAdmin</a> <a href="https://mastodon.social/tags/LinuxSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxSecurity</a> <a href="https://mastodon.social/tags/DevOpsLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOpsLinux</a>

Ian WagnerBurned by Google’s latest(?) project shuttering? I wrote a quick post on how to build container images without resorting to hacks like docker-in-docker or privileged containers. Because somehow the year is 2025 and it’s STILL hard to build images without these hacks and access to a Docker daemon 🤣<a href="https://ianwwagner.com/til/rootless-gitlab-ci-container-builds-with-buildkit" rel="nofollow noopener" translate="no" target="_blank">https://ianwwagner.com/til/rootless-gitlab-ci-container-builds-with-buildkit</a><a href="https://fosstodon.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://fosstodon.org/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a>

4zv4lFor a <a href="https://mastodon.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a>/#selfhosted project, would there be any reason to pick one of <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> or <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> ? (Just because <a href="https://mastodon.social/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> seems amazingly portable it also interests me). So far I mostly run <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> containers with <a href="https://mastodon.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> and VMs with <a href="https://mastodon.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a>, the only *BSD VM running is <a href="https://mastodon.social/tags/opnsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#opnsense</a>. And so far <a href="https://mastodon.social/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#btrfs</a> seems pretty good alternative to <a href="https://mastodon.social/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a>. I hear the network stack is supposed to be better and the system overall more “unified” but I fail to see what to try or do with it.

WulfyYeah... so <a href="https://infosec.exchange/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> is defo not ready for show time."Rootless containers unable to be assigned static IP addresses" (I need it because the NginX address resolver takes too long... intermittent 502 reasons)<a href="https://github.com/containers/podman/issues/7842" rel="nofollow noopener" translate="no" target="_blank">https://github.com/containers/podman/issues/7842</a> (Bug reported 2020!)I am beginning to suspect folks who are enthusiastic about <a href="https://infosec.exchange/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> are enthusiastic about the CONCEPT of Podman, not its production suitability.<a href="https://infosec.exchange/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#podmancompose</a> always seems to be the showstopper.I have invested a lot of time into Podman... but I may need to go back to <a href="https://infosec.exchange/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> and just screw down the containers to minimse <a href="https://infosec.exchange/tags/sploits" class="mention hashtag" rel="nofollow noopener" target="_blank">#sploits</a>

stefenaurisUnderstanding Podman Coming from DockerThis is going to be a bit of a ranty post, but engineers are good at that kind of thing. So here goes.A bit of BackgroundI started my devops career learning about docker and docker-compose. I enjoyed the elegance of being able to write a file of what services I want in a yaml file and bring the entire thing up. Very very easy to rapidly deploy something for testing and into my own production. Use this image, on this port, here’s where to store your data and you can connect to this database. A simple compose file could look like this.<pre><code>services: memos: container_name: memos image: neosmemo/memos:stable ports: - 5230:5230 volumes: - ./memos/:/var/opt/memos restart: unless-stopped</code></pre>Download and run this webapp called memos, use port 5230, store your data in a directory called memos. Restart if anything crashes until I tell the daemon to stop it. Very easy to understand and follow along!Docker has a few consDocker has a few pain points however. The biggest one being that it runs a centralized daemon and if you need to update docker, e.g. a security update is released well… all of your services have to come down for a moment while the patch is applied. That kind of sucks in terms of maintaining stable services and if you have your server set to automatically apply updates (remember automation is good!) who knows when your stuff can go down. Docker also doesn’t come in the default Debian/Ubuntu repositories. You have to install it from a third party repo. This isn’t that big of a deal but the additional configuration is just something you have to remember when setting up a new test environment instead of a simple apt install docker. Lastly docker does support a rootless mode, though it has some limitations. This leads me to my search for alternatives, wondering if there might be something better out there.Enter PodmanSo I decided to examine podman. I wanted to find a way to follow my same workflow (or as close as possible) while using this different implementation of containerization. It addresses my concerns: it comes default in the repos, it natively supports rootless without any monkeying around, and it is daemonless! Sounds good right? Not exactly. Podman-ComposeOkay so as it turns out someone thought of this already! A python program to implement the same thing as docker compose except through podman as your backend. Perfect! Except… every time I try to run a stack I get python errors and crashes…. unless I run it as sudo! So much for trying to escape the need for root there. I’ve tried testing it with a simple deployment of bookstack with a backend mariadb. Never works right! I dont think it properly creates the environment variables defined in the yaml file. So really what’s the point of fighting this? Next!Podman generate/playSo I start searching around to see if there’s a more native implementation of compose like files with podman and I find this redhat article! Written by the people who made the damn thing I expected a nice outline of how to do this. Holy shit was I mistaken reading this:<a href="https://www.redhat.com/en/blog/compose-podman-pods" rel="nofollow noopener" target="_blank">https://www.redhat.com/en/blog/compose-podman-pods</a>This is about as clear as mud. Basically the idea of podman-compose is still being worked about in their development. (To be fair this might have changed in the 5 years since this article was written) but they continue with the concept of podman “pods” and the command “podman generate” which will create a kubernetes style yaml file of what you’ve already created.Well that’s nice but it seems completely ass backwards from what I’m needing here. It seems I’m not the only one who’s had a negative experience:<blockquote><a href="https://www.reddit.com/r/podman/comments/1bk4nee/comment/kvvnxed/" rel="nofollow noopener" target="_blank">Comment</a> by<a href="https://www.reddit.com/user/avamk/" rel="nofollow noopener" target="_blank">u/avamk</a> from discussion<a href="https://www.reddit.com/r/podman/comments/1bk4nee/whats_the_current_canonical_way_to_run_docker/" rel="nofollow noopener" target="_blank"></a> in<a href="https://www.reddit.com/r/podman/" rel="nofollow noopener" target="_blank">podman</a></blockquote>I could continue trying to make this work, but at this point it seems like I’m fighting a fairly pointless battle. Yeah its daemonless, but my workflow isn’t compatible exactly. I could try systemd integration but that’s something I already barely tolerate as it is. I don’t see the point of continuing to fight this when docker already is perfectly functional as it is with a few minor nags. Maybe someday Podman will be able to compete better on this front but for right now, it’s not for me!<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.theheart.land/tag/containerization/" target="_blank">#containerization</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.theheart.land/tag/docker/" target="_blank">#docker</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.theheart.land/tag/linux/" target="_blank">#linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.theheart.land/tag/podman/" target="_blank">#podman</a>

SteveToday I tried to remove a container being run under <a href="https://tech.joerger.us/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a>. I failed (quite miserably) to the point where I had to remove the <a href="https://tech.joerger.us/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> package from my <a href="https://tech.joerger.us/tags/ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#ubuntu</a> desktop in order to get the container to stop automatically relaunching every time I stopped it. WTH am I missing?

Miguel Afonso Caetano"If you're looking to optimize your containerization workflow, here's the good news - the ecosystem has evolved far beyond Docker's original design.Docker revolutionized software deployment by making containerization a standard, but the ecosystem has grown to address specific use cases that Docker wasn't originally designed for. Modern alternatives like Podman, containerd, and CRI-O offer specialized features like daemonless designs, rootless operations, and native Kubernetes integration. These tools don't just offer incremental improvements, but instead they represent fundamental shifts in how we think about container security, performance, and workflow integration.The container ecosystem has matured beyond Docker's monolithic approach, with specialized runtimes optimizing for specific use cases. Whether you're running microservices in production, developing locally, or managing enterprise workloads, there's likely a tool that's better suited to your specific requirements.In this guide, I'll walk you through the most promising Docker alternatives in 2025 and help you choose the right tool for your specific needs."<a href="https://www.datacamp.com/blog/docker-alternatives" rel="nofollow noopener" translate="no" target="_blank">https://www.datacamp.com/blog/docker-alternatives</a><a href="https://tldr.nettime.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://tldr.nettime.org/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://tldr.nettime.org/tags/Containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Containers</a> <a href="https://tldr.nettime.org/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://tldr.nettime.org/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> <a href="https://tldr.nettime.org/tags/Containerd" class="mention hashtag" rel="nofollow noopener" target="_blank">#Containerd</a> <a href="https://tldr.nettime.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://tldr.nettime.org/tags/CICD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CICD</a>

waldiSomeone decided it would be a good idea to use <a href="https://chaos.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> inside a <a href="https://chaos.social/tags/container" class="mention hashtag" rel="nofollow noopener" target="_blank">#container</a>. This of cause results in the rather unpleasant error message:Error: creating runtime static files directory "/var/lib/containers/storage/libpod": mkdir /var/lib/containers/storage: read-only file system

David Chisnall (*Now with 50% more sarcasm!*)Ooo, fun. All of the Linux tools that we ship in the <a href="https://infosec.exchange/tags/CHERIoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#CHERIoT</a> dev container work in the Linuxulator on <a href="https://infosec.exchange/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> with <a href="https://infosec.exchange/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> There appears to be a bug in the Podman with image tags that are multi-arch manifests if you specify <code>--os Linux</code>: it downloads the image and then fails to run it. If you specify the tag for the x86-64 version, it works fine.

dorotaCWeirdest <a href="https://fosstodon.org/tags/bug" class="mention hashtag" rel="nofollow noopener" target="_blank">#bug</a> ever.I have <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> with an open shell sitting in the background. Every couple of hours, it jumps to 100% CPU for absolutely no reason. Even when the screen is locked and I'm away.Until I press enter in the shell.I've never seen a shell come to life for absolutely no reason before. I'm not even sure how I'd start <a href="https://fosstodon.org/tags/debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#debugging</a> it.<a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> <a href="https://fosstodon.org/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a>

Martin BishopInterested in working with <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> on <a href="https://mastodon.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> ? <a href="https://www.youtube.com/watch?v=L5z1_T4nHSU" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=L5z1_T4nHSU</a>

Maxi 11x 💉Boah ey, ich möchte einfach nur rootless <a href="https://chaos.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> nutzen weil es sich ÄUẞERST vernünftig anhört und hatte erwartet, dass das ein Selbstläufer würde, aber es gibt bei der Initialisierung von Containern zig Probleme, die ich erstmal (planlos) lösen muss, nervt sehr. Alles nur, weil die depperte Docker-Crowd eine Pfadabhängigkeit auf Rootuser gewählt hat.

bignoseI'm trying to figure out setting up an email (SMTP) service on my little hosted machines, so I don't need to rely on any particular mail provider.Which leads me to thinking I really like how <a href="https://social.chinwag.org/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> can generate <a href="https://social.chinwag.org/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemD</a> units to automatically manage the service containers.And that has led me to the conclusion I probably should wait for <a href="https://social.chinwag.org/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> Trixie release next month, when I can migrate past Podman 4.3.How do you manage SMTP service for yours, <a href="https://social.chinwag.org/@mike" class="u-url mention" rel="nofollow noopener" target="_blank">@mike</a>?

Recent searches

Search options

Administered by:

Server stats:

#podman