Help from #podman or #docker users welcome!

We have started to offer open alpha access to a hosted Forgejo Actions CI runner. Unfortunately, there are many jobs that can crash the runner for every user reliably, and many users execute them inadvertently.

To save cost and disk wear, we want to keep temporary writes inside the CI builds in RAM and only store the images persistently.

However, the setup is apparently incorrect and we need help figuring it out.

See codeberg.org/actions/meta/issu…

Help with the setup appreciated

Currently, I am the only person actively maintaining the setup, with occasional help from some others for debugging. However, the setup turned out to be more complicated than I anticipated and I would be happy to receive assistance.

^Codeberg.org

Friendica Installation

Ich versuche gerade die #Fediverse Anwendung #Friendica auf meinem #Raspberry Pi 5 in einem #Podman #Container zu installieren. Aber bei der Datenbank ist Schluss. da bleibt es hängen. Weiß jemand Rat? @Friendica Support zum Beispiel?

version: "3.7"

services:

  mariadb:
    image: docker.io/library/mariadb:latest
    restart: always
    volumes:
      - mydb:/var/lib/mysql
    ports:
      - "6033:3306"
    environment:
      MYSQL_ROOT_PASSWORD: *****
      MYSQL_DATABASE: friendica
      MYSQL_USER: friendica
      MYSQL_PASSWORD: *****

  phpmyadmin:
    container_name: phpmyadmin_9092
    image: docker.io/library/phpmyadmin:latest
    restart: always
    ports:
      - "9092:80"
    environment:
      - PMA_ARBITRARY=1
      - PMA_HOST=mariadb
    depends_on:
      - mariadb

  app:
    image: docker.io/library/friendica
    container_name: friendica_9093
    restart: always
    volumes:
      - friendica:/var/www/html    
    ports:
      - "9093:80"
    environment:
      - MYSQL_HOST=mydb
      - MYSQL_USER=friendica
      - MYSQL_PASSWORD=*****
      - MYSQL_DATABASE=friendica
      - FRIENDICA_ADMIN_MAIL=*****
    depends_on:
      - mariadb

volumes:
  mydb:
  friendica:

networks:
  proxy-tier:

I'm experimenting with running my whole #swaywm desktop from a user #podman #container on top of e.g. #Fedora IoT. Works surprisingly well already.

github.com/martinpitt/swaypod

The only dealbreaker is that the container does not receive kernel uevents, i.e. it does not see any kind of hw change. It already uses --network=host and bind-mounts /dev.This is also broken in standard #toolbx. Does anybody know a trick to get that?

GitHub - martinpitt/swaypod: Sway developer desktop in toolbox

Sway developer desktop in toolbox. Contribute to martinpitt/swaypod development by creating an account on GitHub.

^GitHub