Help for docker/podman newbies

[sdgathman]

I've been doing VMs for 30 years (better security, more cpu usage, similar mem usage). I decided to try this container app - the really paranoid can run the container in a VM. :-)

I did "podman compose up -d wishlist" (Fedora and Redhat use podman as docker replacement). It downloads an image and starts a container. There is an apache reverse proxy. Uses a subdomain instead of subdir on the URL.

On connecting it gets 500 Internal Error in the purty purple colors of the app. I have apache logs also, but the URL it stops on is
https://wishlist.example.org/login?redirectTo=%2F

I did find podman tutorials, but nothing seems to address what seems like a brick wall for a podman newbie. Maybe wishlist docs could include a docker/podman tutorial link.

There is mention in docker/podman docs of non-root mode. I tried that, but get a permission denied.

[sdgathman]

More history. It did work with local private IP like in the default yaml config. But that obviously isn't going to fly for deployment. I added the reverse proxy to that private IP, and it didn't work. So then I changed ORIGIN to https://wishlist.example.org. Still no joy. Tried podman update wishlist. Tried podman container rm wishlist, then compose again. I suppose I should check that private IP still works. What is the minimal step to effect a config change on the container? (podman is almost exactly like docker at CLI level by design.)

[cmintey]

Catching up here... did you get it all sorted now? I'll be honest, I've never tried using podman with Wishlist (use it at work though), and I know it can be tricky with it being non-root

[sdgathman]

Back to the Internal Error from container. There is an empty prod.db file in data. It was not empty when app was working. Removing it doesn't help - just creates another empty one.

[cmintey]

Are you still trying to run the container with the "wishlist" user? If so, can you try changing the ownership of the prod.db file to your wishlist user?

[sdgathman]

Runs rootless with selinux enforcing off. I'm going to chalk this up to an selinux bug for now. prod.db was already the wishlist user. Errors were from selinux, not basic unix permissions.

[sdgathman]

https://discussion.fedoraproject.org/t/how-do-i-give-rootless-podman-permissions-to-a-directory/22066/5