-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ls: cannot access '/cloud-encrypt': Transport endpoint is not connected #47
Comments
Your thoughts on what i can do to fix this error? |
A couple of questions: What OS are you running this on and what version of Docker? I'm not sure what Are you sure that your pgid and puid should be 0? Are you able to ssh into the docker container and access /cloud-encrypt? |
OS version that i am running is Linux. OS Kernal version is [admin@RSMediaServer ~]# uname -r Docker version is: [admin@RSMediaServer ~]# docker version Server: --net=lsio in a discussed here: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/ Docker networking If you are using docker-compose, and your services are on the same yaml, you do not need to do this, because docker-compose automatically creates a user defined bridge network and attaches each container to it as long as no other networking option is defined in their config. For the below examples, we will use a network named lsio. We can create it via docker network create lsio. After that, any container that is created with --net=lsio can ping each other by container name as dns hostname. Keep in mind that dns hostnames are meant to be case-insensitive, however container names are case-sensitive. For container names to be used as dns hostnames in nginx, they should be all lowercase as nginx will convert them to all lowercase before trying to resolve. On the PGID and PUID i am using, I am aware of this article that explains how they work: https://medium.com/@mccode/understanding-how-uid-and-gid-work-in-docker-containers-c37a01d01cf I am running the docker container as the admin user which is basically a user that has root access: [admin@RSMediaServer ~]# id -a admin I am able to SSH into the docker container and access /cloud-encrypt [admin@RSMediaServer ~]# docker exec -it cms /bin/bash Can you please send me a way to chat with you online or a direct email that i can contact you at? I would like to get the issue resolved in Docker container up and running. Unable to copy files to local-media directory. Permissions show ok via ls-l. #49 ASAP. Thanks. |
Is it correct that you are running it on a Qnap NAS? Have you tried that? |
So what would the mount commands that you referred to for the following volumes be? Should the docker create code have --mount commands? If so, what should they be? See: https://docs.docker.com/storage/volumes/ -v "/share/media":/local-media:shared I tried this at my SSH command prompt and received the following: [admin@RSMediaServer ~]# sudo mount --make shared /share/media [admin@RSMediaServer ~]# sudo mount --make shared /local-media |
You should just run the command by itself on your shared bindings and then afterwards run docker create/run You need to type |
Initially entered the following docker commands to download and create volumes for cloud-media-scripts
sudo docker pull madslundt/cloud-media-scripts
sudo docker volume create --name local-media
sudo docker volume create --name local-decrypt
sudo docker volume create --name config
sudo docker volume create --name chunks
sudo docker volume create --name datadb
sudo docker volume create --name log
sudo docker volume create --name cloud-encrypt
sudo docker volume create --name cloud-decrypt
Then
ran
sudo docker create --name cloud-media-scripts
--restart=always
--net=lsio
--privileged --cap-add=MKNOD --cap-add=SYS_ADMIN --device=/dev/fuse
-e PUID=0
-e PGID=0
-e CLEAR_CHUNK_MAX_SIZE="1000G"
-e REMOVE_LOCAL_FILES_WHEN_SPACE_EXCEEDS_GB="2000"
-e FREEUP_ATLEAST_GB="1000"
-v "/share/media":/local-media:shared
-v /mnt/external/media:/local-decrypt:shared
-v /mnt/external/media/cloud-encrypt:/cloud-encrypt:shared
-v "/share/appdata/cms":/config
-v /mnt/external/plexdrive:/chunks
-v /logs:/log
madslundt/cloud-media-scripts
I then successfully ran
sudo docker exec -ti cloud-media-scripts rclone_setup
following instructions here:
https://github.com/madslundt/docker-cloud-media-scripts
and then successfully ran
sudo docker exec -ti cloud-media-scripts plexdrive_setup.
Now when i start the docker container, I am seeing:
User gid: 0
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Started mongod --logpath /log/mongod.log
Started mount
2019-10-23T16:15:39.390+0000 I CONTROL [main] log file "/log/mongod.log" exists; moved to "/log/mongod.log.2019-10-23T16-15-39".
[ 2019-10-23@16:15:45 ] Mounting Google Drive mountpoint: /cloud-encrypt
ls: cannot access '/cloud-encrypt': Transport endpoint is not connected
Waiting for mount /cloud-encrypt ...
I tried via ssh to execute
fusermount -uz /mnt/external/media/cloud-encrypt
which executed successfully. I then stopped and restarted the container and still get the error message
ls: cannot access '/cloud-encrypt': Transport endpoint is not connected
Can you tell me how to fix this error?
What is the best way to contact you for your assistance? Discord? If so, what ID?
The text was updated successfully, but these errors were encountered: