flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

#podman

13 posts12 participants0 posts today

I've decided that rather than just taking notes in my own wiki to be forgotten I'm going to start a rudimentary blog.

Here's post 1 of 2 on running #traefik in #podman with Quadlets. The end goal in part 2 will be getting #headscale running for a fully controlled #tailscale VPN. Stay tuned!

roguesecurity.dev/blog/headsca

roguesecurity.devHow to Host Headscale on a Linux Server with Podman Quadlets (Part 1)My strategy for self-hosting a tailscale control-plane server using headscale, deployed with podman quadlets (Part 1)
Replied in thread

Incredible how Alexander Larsson was ahead of times with that reply about sharing libraries, it's basically the approach by Docker images... but OSTree, used by Flatpak, predates Docker and it is even more efficient with its by-file deduplication. And the recent #ComposeFS by the same author will allow #Podman containers to have the same deduplication not only on disk but even on RAM (to my understanding)

Finally moved my home server off of docker and onto podman. The holdout was Taiga which was using docker compose. Despite already deploying a few simpler services with podman, I still didn't know before this how podman does hostnames, how to set up a network with a quadlet, and using PVCs.

TECH RANT: Every time I try to use a GUI tool to create a container of some sort (#Docker desktop, Cockpit's #podman module, etc.) it fails, but if I fall back to the terminal & type it all out it works just fine.

Am I a glutton for punishment, or just too stupid for GUI?

Ive built a setup for hosting websites which consists of:
* Host running #microos with #podman
* #Treafik and #sshpiper at the edge
* #Nginx, php-fpm, #mariadb + phpmyadmin + nginx or #postgres + dbadmin, openssh for each site

It actually works quite well, openssh keybased access is to transfer files into the containers, traefik does the reverse proxying.

I'm just wondering if its a sustainable and maintainable setup. Sometimes just going with a "standard" solution seems so much easier.

Estoy experimentando con el CMS #Ghost. Si queréis instalar el contenedor #Docker sobre #Podman en #Fedora, este es el comando que mejor me ha ido hasta ahora:

podman run -d --name nombre-contenedor --userns=keep-id -e NODE_ENV=development -e url=http://localhost:3001 -p 3001:2368 -v /ruta/dentro/de/tu/directorio/personal:/var/lib/ghost/content:Z docker.io/ghost

🌕 Podman Quadlets 與 Podman Desktop
➤ 簡化容器管理,提升開發效率
podman-desktop.io/blog/podman-
Podman Quadlets 是一種利用 Systemd 聲明式管理容器的新方法,適用於小型應用或開發環境,避免了 Kubernetes 的複雜性。Podman Desktop 擴展 “Podman Quadlet” 簡化了 Quadlets 的管理,提供視覺化界面來列出、生成、編輯和監控 Quadlets,讓使用者更容易地利用 Systemd 管理容器,實現自動啟動、重啟等功能。
+ 感覺這個 Quadlets 真的解決了在單機開發環境下使用 Kubernetes 的過重問題,Podman Desktop 的整合讓操作更方便了!
+ 終於可以告別繁瑣的指令了,透過圖形界面管理容器,對於新手來說很友善。
#Podman #容器 #Systemd #DevOps

podman-desktop.io · Podman Quadlets with Podman Desktop | Podman DesktopLearn how to create & manage and use Quadlets with Podman Desktop

🔍 Looking for #Linux #Containers for your CI/CD pipeline? #foundata built a collection of OCI images with

✅ functional systemd (not just a shim!)
✅ unprivileged execution support – perfect for tools like #Podman.

👉 Explore all Integration Test Target (ITT) container files on github.com/orgs/foundata/repos

💡 Also ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

Open Source. Automation. Agile. foundata GmbH has 25 repositories available. Follow their code on GitHub.
GitHubfoundata GmbHOpen Source. Automation. Agile. foundata GmbH has 25 repositories available. Follow their code on GitHub.

my #build #container framework:

sudo unshare \
  --fork \
  --mount \
  --uts \
  sh -c "
    mkdir -p $ROOTFS/proc
    mkdir -p $ROOTFS/sys
    mkdir -p $ROOTFS/dev
    mount -t sysfs /sys $ROOTFS/sys
    mount -t proc /proc $ROOTFS/proc
    mount --rbind /dev $ROOTFS/dev
    hostname $MACHINE
    su $USER
    export PUAVO_CACHE_PROXY=$PUAVO_CACHE_PROXY
    sudo unshare --root $ROOTFS $CMDLINE
  "

Nests nicely with #Docker and #Podman :-)

Been testing out the #virtiofs support now baked into #proxmoxVE. It works, had to do some #selinux adjustments on #fedora to allow my #podman containers to use the mountpoint. Added this policy

```
(allow container_t unlabeled_t ( dir ( read write )))
```

In raw speed it is definitely not a winner - #nfs is easily double the speed. But on this particular VM I don't need the speed - it is nice that this is all self-contained now, and I can actually remove NFS altogether.