Wulfy<p>Yeah... so <a href="https://infosec.exchange/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> is defo not ready for show time.</p><p>"Rootless containers unable to be assigned static IP addresses" (I need it because the NginX address resolver takes too long... intermittent 502 reasons)</p><p><a href="https://github.com/containers/podman/issues/7842" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/containers/podman/i</span><span class="invisible">ssues/7842</span></a> (Bug reported 2020!)</p><p>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">#<span>Podman</span></a> are enthusiastic about the CONCEPT of Podman, not its production suitability.</p><p><a href="https://infosec.exchange/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmancompose</span></a> always seems to be the showstopper.</p><p>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">#<span>Docker</span></a> and just screw down the containers to minimse <a href="https://infosec.exchange/tags/sploits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sploits</span></a></p>
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software.
If you wish to join, contact us for an invite.
Administered by:
Server stats:
8.6Kactive users
fosstodon.org: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.3
#podmancompose
0 posts · 0 participants · 0 posts today
Wulfy<p>So yeaaah....<br><a href="https://infosec.exchange/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> <br><a href="https://infosec.exchange/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmancompose</span></a> is DEFINITELY NOT ready for showtime...</p>
Zło To<p><a href="https://101010.pl/tags/til" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>til</span></a> podman lepiej wspiera pliki kubernetes niż pliki docker compose. I super, bo właśnie korzystam z niego do testowania, a środowisko produkcyjne mam na k8s, czyli nie muszę mieć oddzielnego pliku dla compose</p><p><a href="https://101010.pl/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> <a href="https://101010.pl/tags/podmanCompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmanCompose</span></a> <a href="https://101010.pl/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://101010.pl/tags/dockerCompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dockerCompose</span></a> <a href="https://101010.pl/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://101010.pl/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a></p>
The GentleHacker<p>I have spent much of my Sunday speedrunning the documentation for <a href="https://tech.lgbt/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a>, <a href="https://tech.lgbt/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a>, <a href="https://tech.lgbt/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmancompose</span></a> and <a href="https://tech.lgbt/tags/finch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>finch</span></a> and I am mad about it.</p><p>I'm also mad about how the entire ecosystem feels linearly fractured between "here, built and run a container, so flexible and dynamic" and "Describe your needs in excruciating detail. Include these 18 options we refuse to document adequately or perish. No, we won't be giving you any semantic or cli sugar to make things more securable. Fuck you; hire an Ops Team".</p><p>I know I'm no <a href="https://tech.lgbt/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a> expert; but when _every_ option causes that vague "Ur doin it rong" tension, it begins to feel like the problem is at least partially bad <a href="https://tech.lgbt/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>documentation</span></a> and partially paradigmical ossification.</p><p>Oh and <a href="https://tech.lgbt/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> can fuck right off; I'm hosting some software not launching a moon into another galaxy using only breakfast cereal and cotton gins.</p>
Paula Gentle on Friendica<p>In meinem Fall war das eindeutig selbstverschuldet und noch nicht mal kaputt, aber halt nicht das, was ich erreichen wollte.</p><p>Ich wollte auf 28.0.5, aber in der <a href="https://libranet.de/search?tag=podman-compose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman-compose</span></a> war ':latest' definiert und vor zwei Tagen kam 29.0.0 raus, also wurde erfolgreich auf die neue Version migriert. Nur will ich die (jetzt noch) nicht und es gibt scheinbar keinen einfachen Weg zurück, weil <a href="https://libranet.de/search?tag=Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nextcloud</span></a> nicht abwärtskompatibel ist.</p><p>Dann teste ich jetzt mal das <a href="https://libranet.de/search?tag=Restore" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Restore</span></a> mit <a href="https://libranet.de/search?tag=restic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>restic</span></a>...</p>
scy @ WHY2025 (7299)<p>Anyone running <a href="https://chaos.social/tags/PaperlessNGX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PaperlessNGX</span></a> <a href="https://chaos.social/tags/rootless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rootless</span></a> using <a href="https://chaos.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> and <a href="https://chaos.social/tags/PodmanCompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PodmanCompose</span></a> under <a href="https://chaos.social/tags/Debian12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian12</span></a>? The volumes I'm mapping to the host always get chowned to 100999:100999, and that's with USERMAP_UID=1000 and USERMAP_GID=1000 in docker-compose.env.</p><p>Playing around with PODMAN_USERNS mainly leads to the container not starting at all (in at least one case because it can't install packages).</p><p><a href="https://chaos.social/tags/paperless_ngx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paperless_ngx</span></a></p>
Paula Gentle on Friendica<p>Nun gut - der Schritt von <a href="https://libranet.de/search?tag=docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> zu <a href="https://libranet.de/search?tag=podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> ist getan und Dank <a href="https://libranet.de/search?tag=podman-compose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman-compose</span></a> läuft unsere <a href="https://libranet.de/search?tag=Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nextcloud</span></a> quasi 1:1 seit 8 Monaten stabil.</p><p>Es wird Zeit, den zweiten Schritt zu tun: Den Compose-Rotz in einen <a href="https://libranet.de/search?tag=Pod" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pod</span></a> zu migrieren, um dann rootless Port 80 und 443 anzubieten und einfache <a href="https://libranet.de/search?tag=systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> - Integration in einem Rutsch zu erhalten.</p><p>Hab' ja noch keinen Schimmer, wie ich vorgehen soll...</p>
worldofgeese :guix:<p>I accept the fragmentation. Posting <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="tag">#<span>podman</span></a> <a href="https://fosstodon.org/tags/podmancompose" class="mention hashtag" rel="tag">#<span>podmancompose</span></a>, <a href="https://fosstodon.org/tags/guix" class="mention hashtag" rel="tag">#<span>guix</span></a> stuff to Twitter was so foolish because where are the <a href="https://fosstodon.org/tags/foss" class="mention hashtag" rel="tag">#<span>foss</span></a> folks? They're here.</p>
Mr.P<p>Mit heute ist jetzt jedes von mir direkt genutzte Gerät <a href="https://chaos.social/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Docker</span></a> frei.</p><p>Kein Docker, Docker-Compose, Docker-Maschine mehr. Nur noch <a href="https://chaos.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> und <a href="https://chaos.social/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmancompose</span></a> </p><p>👀 at you my little remaining servers</p>
jose<p>summoning <a href="https://fosstodon.org/tags/podmancompose" class="mention hashtag" rel="tag">#<span>podmancompose</span></a> hashtag :ablobcateyesflip:</p>
Maidox<p>Anyone here setup <a href="https://fosstodon.org/tags/nextcloud" class="mention hashtag" rel="tag">#<span>nextcloud</span></a> with <a href="https://fosstodon.org/tags/podman" class="mention hashtag" rel="tag">#<span>podman</span></a> or <a href="https://fosstodon.org/tags/podmancompose" class="mention hashtag" rel="tag">#<span>podmancompose</span></a> ? I'm wondering how it would be different from <a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="tag">#<span>docker</span></a> or <a href="https://fosstodon.org/tags/dockercompose" class="mention hashtag" rel="tag">#<span>dockercompose</span></a> as I'd prefer my next setup to be <a href="https://fosstodon.org/tags/containerized" class="mention hashtag" rel="tag">#<span>containerized</span></a> rather than anything else.<br /><a href="https://fosstodon.org/tags/containers" class="mention hashtag" rel="tag">#<span>containers</span></a></p>
w4tsn ~> :idle:<p><span class="h-card"><a href="https://metalhead.club/@Aarkon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Aarkon</span></a></span> nicht mit <a href="https://darmstadt.social/tags/rocketchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rocketchat</span></a> aber mit <a href="https://darmstadt.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> und <a href="https://darmstadt.social/tags/raspberrypi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>raspberrypi</span></a> im allgemeinen.</p><p>Privat betreibe ich ein <a href="https://darmstadt.social/tags/FedoraIoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FedoraIoT</span></a> OS mit <a href="https://darmstadt.social/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> (docker Alternative), <a href="https://darmstadt.social/tags/podmancompose" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podmancompose</span></a> (pendant zu docker) und <a href="https://darmstadt.social/tags/traefik" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>traefik</span></a> als docker native proxy.</p><p>Was willst du denn wissen?</p><p>In jedem Fall wirst du ein arm / raspberry Pi kompatibles Image brauchen. Der Rest funktioniert dann nach Doku.</p><p>Schau dir zum Beispiel mal das folgende Docker hub Image an, das ist recht aktuell.</p><p><a href="https://hub.docker.com/r/webhippie/rocketchat" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hub.docker.com/r/webhippie/roc</span><span class="invisible">ketchat</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
LoginDrag & drop to upload