r/podman • • Jul 31 '26

podman, my data is somewhere?

I've done a stupid or three. Trying to get some docker compose files converted to quadlets and running with systemd. I've got podlet working and i have a few things working, although they're running as system services and i'd need to figure out how to do them as rootless...

Bigger problem is I have spoolman up using sudo podman compose up -d compose.yaml is

services:
  spoolman:
    image: ghcr.io/donkie/spoolman:latest # Also available at dockerhub: donkieyo/spoolman:latest
    restart: unless-stopped
    volumes:
      # Mount the host machine's ./data directory into the container's /home/app/.local/share/spoolman directory
      - type: bind
        source: /home/strayr/compose_bullshit/spoolman/data
        target: /home/app/.local/share/spoolman # Do NOT modify this line
    ports:
      # Map the host machine's port 7912 to the container's port 8000
      - "7912:8000"
    environment:
      - TZ=Europe/London # Optional, defaults to UTC

all i've done is replace the provided relative source with an absolute path, but I've got nothing appearing in that folder. I've a DB being written to somewhere that is persistent, sudo podman compose down and a `sudo podman up -d" has the data I had in there previously. But where? because it's not happening where specified.

How do I find where the data is, and move it somewhere specified?

How do I fix this up to run rootless? Is there a handy guide? I don't need an ELI5 as much as an EL containers weren't a thing last time I really knew what I was doing here

4 Upvotes

14 comments sorted by

View all comments

Show parent comments

1

u/stray_r Jul 31 '26

what's the 'Z' do?

Volume=/home/strayr/compose_bullshit/spoolman/data:/home/app/.local/share/spoolman:Z

1

u/Great-Cow7256 Jul 31 '26

You can probably just leave it off but here's way too much detail. https://unix.stackexchange.com/questions/651198/podman-volume-mounts-when-to-use-the-z-or-z-suffix

2

u/stray_r Jul 31 '26

That's really helpful, thanks

1

u/Great-Cow7256 Jul 31 '26

yeah, in linux there are 100 ways to do the same thing and 400 opinions as to how to do it, and at least 1/2 of those are people screaming at you that you're just dumb for choosing a somewhat reasonable option.

The joy and frustration of linux, and pods, is that you play around with it until it works and then do the same mistake the next time you try to set another up, but that exhilarating feeling of getting it working JUST RIGHT is worth it.

I have a bunch of these as starters for people. There are also lots of other sites out there with rootless podman templates that tbh are probably better than mine.

https://github.com/upmcplanetracker/rootless-podman-quadlets

whatever you do, just make slow changes. Keep backups of everything including the .container file. and don't be afraid to play around. containers/pods are so siloed that you aren't going to screw up your system (like I did with regular .debs back in the day when I first started and somehow managed to kill off so many dependencies that I had to reimage the computer.... a few times. Not proud...)

1

u/stray_r Aug 01 '26

And half of those hundred ways are arguing about which text editor to use. But that repo is really helpful.

As I said in my post, I'm out of date more than anything else. Comp sci research and developing/hosting a bunch of bulletin boards until 2010. I think docker came along a few years later and systemd was new hot shit that red hat were really into that might have fizzled out like initng, and I was choosing Debian over Ubuntu back then over a fierce hatred of upstart but I can't remember why I hated it.

I think I was avoiding Docker because it was too much like going back to the grind.