Hi everyone,

This would seem to be a basic question (I’ve been on this for a few hours and can’t seem to get it working).

This is my file for my pod:

$ cat backup.pod

[Unit]
Description=backup pod

[Pod]
Network=slirp4netns:port_handler=slirp4netns
PodmanArgs=--userns=auto:size=10000
PodName=backup

And this is the file for my container which is supposed to be part of the pod:

$ cat backup.container

[Unit]
Description=backup container

[Container]
Image=docker.io/debian/debian:latest
ContainerName=backup-container
Entrypoint=/bin/bash
Exec=/bin/bash -c "apt-get update -y && apt-get upgrade -y && apt-get install rclone vim -y && exec bash"
Pod=backup
GlobalArgs=-d -t

[Service]
Restart=always

[Install]
# Start by default on boot
WantedBy=multi-user.target default.target
  1. Podman’s systemd-generator doesn’t seem to create any service file for backup.pod in /run/user/$(id -u user). I do see a service file for backup.container, backup.service.
  2. Regardless, systemctl start backup.service errors out anyway.

I’m unable to understand how to use quadlet from the documentation. AFAIK I did everything they asked (https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html).

The primary reason why I tried this was because I couldn’t figure out how to create a pod using compose.yaml either. If someone has answers to these questions, they would be much appreciated!

Thanks!

  • MigratingtoLemmy@lemmy.worldOPEnglish
    0·
    5 months ago

    Apologies for not answering earlier. I have since switched over to podman generate kube and podman play kube for managing my podman infrastructure. This plays in well with my plans since I can’t be dependent on systemd going forward. Thank you for your help.

    With that said, I wanted to ask another question: when I try to run a container with podman run debian, it automatically pulls the debian container without a problem, however how is it that when I type podman pull docker.io/debian/debian it requires auth?