Change ports in docker-compose.yml

[PEQSPC]

Can i change ports in docker-compose.yml because is causing conflict in my alma linux?

when a run podman-compose up -d

[evilaliv3]

@PEQSPC : i actually do not think the problem is on the ports.

@rglauco by any chance do you have any advice?

[rglauco]

@PEQSPC I tried on Almalinux 9 with default docker-compose.yml, no problem at all when changing exposed ports.
The error is related to something else, could you please paste the container logs?

[PEQSPC]

the logs of my container as only that message :

[PEQSPC]

[PEQSPC]

What steps did you take to install? @rglauco

[rglauco]

With the default Dockerfile and docker-compose.yml, i've only launched podman-compose up -d.
I tried as root and as regular user with custom ports in both setups with podman version 4.6.1.

Your error seems to be related inside the container, do you use a custom Dockerfile?

[PEQSPC]

No,i use the default dockerfile in the this git repository

[PEQSPC]

i will try to create a ubuntu server container and then install with this InstallationGuide https://docs.globaleaks.org/en/main/setup/InstallationGuide.html

[rglauco]

Could you give podman-compose down -v and delete the globaleaks image?
Then give podman-compose up and copy-paste the logs (as text file, not image, for better readability)?

[PEQSPC]

logsglobal.txt

[PEQSPC]

its working now i think

[rglauco]

Yes, it seems so. Now you can try to change exposing host ports.

[PEQSPC]

how i backup the container with all this data ?

[rglauco]

I believe with podman-commit --include-volumes.
Maybe it's better to save only data volume, i'll let you find a proper way to do so: with podman volume inspect docker_globaleaks you find the volume location (i guess /home/admin/.local/share/containers/storage/volumes/docker_globaleaks/_data) there you find the data.

[PEQSPC]

ok, thank you very much for your help