Recent searches

No recent searches

Search options

Only available when logged in.
sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Administered by:

Server stats:

577
active users

sigmoid.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.3

#podmancompose

0 posts0 participants0 posts today
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>
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>
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>
scy<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>
TrendingLive feeds
About