Sigmoid Social

.:\dGh/:.Very glad that Docker (and containers) exists.You don't know how tedious is to set up a development environment to fix one line.It would be great if you could mount a file as a filesystem but I guess the performance penalty would be greater than... well, just mounting a folder.<a href="https://mastodon.social/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a> <a href="https://mastodon.social/tags/Containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Containers</a> <a href="https://mastodon.social/tags/OCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OCI</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://mastodon.social/tags/Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#Code</a> <a href="https://mastodon.social/tags/Rancher" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rancher</a> <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a>

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>

Podman_ioPodman v5.6 is getting closer, and today, Podman v5.6.0 RC2 dropped! A number of speed improvements in image builds, new quadlet commands, and several bug fixes. Release Notes with details: <a href="https://github.com/containers/podman/releases/tag/v5.6.0-rc2" rel="nofollow noopener" translate="no" target="_blank">https://github.com/containers/podman/releases/tag/v5.6.0-rc2</a> <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Timo TijhofTIL that golang supports importing from a custom domain while still using GitHub underneath (or any Git host), so that your public import path isn't bound to GitHub.TL:DR; You put an HTML <meta> tag on your website that points to your Git repo.From <a href="https://fosstodon.org/@Podman_io" class="u-url mention" rel="nofollow noopener" target="_blank">@Podman_io</a><a href="https://blog.podman.io/2025/08/upcoming-migration-of-three-containers-repositories-to-monorepo/" rel="nofollow noopener" translate="no" target="_blank">https://blog.podman.io/2025/08/upcoming-migration-of-three-containers-repositories-to-monorepo/</a><a href="https://fosstodon.org/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#golang</a> <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://fosstodon.org/tags/monorepo" class="mention hashtag" rel="nofollow noopener" target="_blank">#monorepo</a> <a href="https://fosstodon.org/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</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>

openSUSE LinuxSchedulers as <a href="https://fosstodon.org/tags/containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#containers</a>? Yes! With <a href="https://fosstodon.org/tags/SchedKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#SchedKit</a>, you can download, run, and attach custom <a href="https://fosstodon.org/tags/schedulers" class="mention hashtag" rel="nofollow noopener" target="_blank">#schedulers</a> using <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>, or <a href="https://fosstodon.org/tags/containerd" class="mention hashtag" rel="nofollow noopener" target="_blank">#containerd</a>. All made possible by <a href="https://fosstodon.org/tags/eBPF" class="mention hashtag" rel="nofollow noopener" target="_blank">#eBPF</a> and sched_ext. Watch this <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#oSC25</a> video to learn more. <a href="https://youtu.be/_pKuF8y-2bM?si=bYEpm9hHpg4Gfk_H" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/_pKuF8y-2bM?si=bYEpm9hHpg4Gfk_H</a>

coldclimateSunday afternoon tech yak shaving. I want to write blog post about making trifle (really) but I hate the idea I write it and shitty AI companies scrape it. So I started to try and work out how to glue <a href="https://hachyderm.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#anubis</a> together with Caddy for multiple domains, but I don't really want to install Docker on this new machine, so I headed down the route of <a href="https://hachyderm.io/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> installed via brew.And now, no matter what is in my compose.yaml file I get...WARNING:podman_compose:missing services [compose.yaml] Error: executing /opt/homebrew/bin/podman-compose up compose.yaml: exit status 1Which is all very vexing when really I just want to blog about jasmine scented custard

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>

Gosz<a href="https://mastodon.social/tags/unifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#unifi</a> selfhost <a href="https://news.ycombinator.com/item?id=44746603" rel="nofollow noopener" translate="no" target="_blank">https://news.ycombinator.com/item?id=44746603</a> <a href="https://mastodon.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> "self-host the complete UniFi network stack on your own hardware. (UniFi Network and InnerSpace, you can also run UniFi Identity)"

openSUSE LinuxIntroducing <a href="https://fosstodon.org/tags/container" class="mention hashtag" rel="nofollow noopener" target="_blank">#container</a>‑snap. It's a prototype plugin for atomic OS updates via <a href="https://fosstodon.org/tags/OCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OCI</a> images! It integrates with <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a>’s tukit and <a href="https://fosstodon.org/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a>’s <a href="https://fosstodon.org/tags/Btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Btrfs</a> driver to boot your host from a container image. Check out this <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#oSC25</a> talk. <a href="https://youtu.be/u_9BoxsHQI8?si=l1TqCBmHQWidDc-x" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/u_9BoxsHQI8?si=l1TqCBmHQWidDc-x</a>

Elias Probst<a href="https://mastodon.social/@carstenraddatz" class="u-url mention" rel="nofollow noopener" target="_blank">@carstenraddatz</a> the problem is not so much preventing access to the filesystem, it's the fact that <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> simply fails when it cannot open the DB as read-write.

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>

Elias ProbstWhy on Earth does <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> require read-write access to storage/libpod/bolt_state.db for read-only operations like "podman images"?

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.

Podman_ioHey all! We've an exciting Podman Community Meeting coming up in one week and a few minutes from now on Tues, Aug 5, 11:00 am EDT (UTC-4). We'll be talking Orches, MCP, and Reproducible Container Builds. Agenda with meeting info: <a href="https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both" rel="nofollow noopener" translate="no" target="_blank">https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both</a> <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

AheadofthekrautsI absolutely hate the docker/podman images alias. I always fall for it.>podman image list list all images>podman images list list all images named list :blobcattableflip:>podman images list all images<a href="https://social.tchncs.de/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://social.tchncs.de/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#podman</a> <a href="https://social.tchncs.de/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> <a href="https://social.tchncs.de/tags/papercuts" class="mention hashtag" rel="nofollow noopener" target="_blank">#papercuts</a> <a href="https://social.tchncs.de/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a>

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>

Recent searches

Search options

Administered by:

Server stats:

#podman