Open NewToStuff opened 2 years ago
Hello @NewToStuff, maybe you have forgotten --privileged flag? Unfortunately, it must be provided for FUSE mount to work in the container.
Hi,
Thanks for the tip. I have changed the command to: pcloudcc -u testemail@gmail.com -s -m pcloud-mount-dir --privileged
I now get the following:
pCloud console client v.2.0.1 error: unrecognised option '--privileged'
Thanks
If I remove the privileged flag but make sure that privileged and init options are enabled in the GUI for portainer in the Runtime then I get these errors again:
pCloud console client v.2.0.1 init failed
The --privileged flag is supposed to be passed to docker engine while creating container.
Hi, I think that is what the settings I mentioned do??? I am not certain though. Your help is very much appreciated.
Thanks
I'm afraid I'm not familiar with Portainer. The privileged mode looks right turned on, but I don't know what that Init toggle does.
And, BTW, on the first run you need to have console access to the container, to be able to enter the password for the first time. This might be your issue...
Hi, I am trying to run pCloud as a docker using portainer on a Synology NAS. I am not sure whether it should be possible.
I have created the container and set the following in portainer:
Command: pcloudcc -u testemail@gmail.com -s -m pcloud-mount-dir
Host/volume | Path in container /volume1/docker/pcloud/mount | /pcloud-mount-dir /volume1/docker/pcloud/cache | /root/.pcloud
Console: Interactive & TTY (-i -t)
When starting the console the following appears in the log: pCloud console client v.2.0.1 init failed
I suspect my issue is due to the volume definition or the establishment of an interactive session to add the password for the pCloud repository.
Any thoughts much appreciated.