Hello everyone,

I am currently trying to transition from docker-compose to podman-compose before trying out podman quadlets eventually. The first couple containers work great but today I tried Linkding and I run into a weird error.

Linkding can’t access the data directory because the permission gets denied. After inspecting the container all the directories inside belong to root. But podman runs rootless so that must be the issues. I tried to change the owner of the data directory on the host to root but then the data directory in the container belongs to nobody and nogroup (?). After checking the environment variable documentation of Linkding it seems like there is no environment variable for a UID and GID.

I think I have a fundamental misunderstanding how rootfull and rootless containers work so I would be very grateful if anybody could point me in the right direction on where to get a solution for this problem or anybody had success running Linkding rootless.

Thanks a lot in advance!

Edit:

I used named volumes because that’s what the dev used in the example compose file. Now I tried to use named volumes instead and now everything seems to work fine. No error in the logs and the web ui is accessible.

  • kumi@feddit.onlineEnglish
    4·
    1 day ago

    I am currently trying to transition from docker-compose to podman-compose before trying out podman quadlets eventually.

    Just FYI and not related to your problem, you can run docker-compose with podman engine. You don’t need docker engine installed for this. If podman-compose is set up properly, this is what it does for you anyway. If not, it falls back to an incomplete Python hack. Might as well cut out the middle-man.

    systemctl --user enable --now podman  
DOCKER_HOST=unix://${XDG_RUNTIME_DIR}/podman/podman.sock docker-compose up
    • theorangeninja@sopuli.xyzOPEnglish
      1·
      21 hours ago

      I was unsure if I installed docker on this machine so I ran docker-compose and the help page showed up (another one than for podman-compose). Then I queried my installed packages and grepped them for docker and nothing shows up. Only podman-compose has docker in the description. So I accidentaly used that compatibility layer already without knowing.

      But one reason I consider to switch is because compose files are not really standardized I heard and quadlets are structured like systemd files so I seems more applicable. But that is still a long way.