Container doesn't work (due to permission issue ?) about docker-nginx-fpm-alpine HOT 2 CLOSED

Hi Julien,

The first part of the logs (till 09:35:27) are expected. As you correctly deduced from the second part of the logs, the permissions of your persistent volume aren't correct. I don't know if your synology lets you access the underlying Linux via shell, so here are two ways you can change those permissions:

1. If you do get some kind of shell access, for example via ssh or a web terminal, you just need to execute a chown command: chown 65534:82 /[path on the synology that you use as a volume].
2. If you can't directly execute commands, but can run containers, just run that command in a container with its root user. For example start the busybox container with the same path as the privatebin volume, but attached to the busybox /mnt path and let it run the command chown 65534:82 /mnt for you. Once this has run for the first time, the privatebin container will have the permissions to write into that path.

Finally, if you don't intend to preserve any of the content stored in privatebin when upgrading it, you can run the container without a persistent volume. Every time you upgrade privatebin you would start from a clean state and all previous pastes would be lost, but you wouldn't have to deal with permissions.

from docker-nginx-fpm-alpine.

Hi @elrido ,
I'm so sorry to not answer you, I could solve my issue thanks to your help.

Have a nice day.
Julien

from docker-nginx-fpm-alpine.