Can't connect to terminal "Socket Close"

Discussion room for Docker, a lightweight virtualization application that gives you the ability to run thousands of containers created by developers from all over the world on DSM
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
roninXpl
Beginner
Beginner
Posts: 26
Joined: Thu Feb 11, 2016 7:56 pm
Contact:

Can't connect to terminal "Socket Close"

Unread post by roninXpl » Sat Feb 13, 2016 9:57 am

Anyone knows how to restart the whole Docker package/service in DSM?
After some time I now can't connect to container's terminal; I get "Socket Close" message.
Restarting the container doesn't help and I don't want to restart the whole NAS.

rowox
Knowledgeable
Knowledgeable
Posts: 335
Joined: Sat Sep 03, 2011 6:15 am

Re: Can't connect to terminal "Socket Close"

Unread post by rowox » Sat Feb 13, 2016 4:04 pm

Go to Start --> Packages then select the Docker pagkage, stop it and then start it. Just like any other package.
Do you agree that you should be able to encrypt your important folders, such as Photo, Home (and Video and Music)? PLEASE VOTE and comment at the following thread and make your voice heard (you'll need to cut and paste the URL):
http://forum.synology.com/enu/viewtopic.php?f=3&t=93366

DS415+, 4 x 6TB Red

roninXpl
Beginner
Beginner
Posts: 26
Joined: Thu Feb 11, 2016 7:56 pm
Contact:

Re: Can't connect to terminal "Socket Close"

Unread post by roninXpl » Sun Feb 14, 2016 12:34 pm

rowox wrote:Go to Start --> Packages then select the Docker pagkage, stop it and then start it. Just like any other package.
Thanks.
It looks like I can attach to the container from the shell but not via the web UI.
Where do I submit big reports for packages?

BreizhCat
I'm New!
I'm New!
Posts: 1
Joined: Thu May 12, 2016 10:26 am

Re: Can't connect to terminal "Socket Close"

Unread post by BreizhCat » Thu May 12, 2016 10:30 am

Hello

I had the same issue on my docker.
I remove the file(s) in

Code: Select all

/var/lib/docker/network/files/
After that, i had access back to the terminal.

Hope it can help !

Yann

ismithers
Experienced
Experienced
Posts: 114
Joined: Mon Jun 03, 2013 9:56 am

Re: Can't connect to terminal "Socket Close"

Unread post by ismithers » Mon May 16, 2016 3:53 pm

BreizhCat wrote:Hello

I had the same issue on my docker.
I remove the file(s) in

Code: Select all

/var/lib/docker/network/files/
After that, i had access back to the terminal.

Hope it can help !

Yann
Hey Yann, thanks for the post however this doesn't resolve it for me. The files directory appears as soon as I start Docker again, and then I get Socket Close.

astropixel
I'm New!
I'm New!
Posts: 1
Joined: Fri Dec 08, 2017 9:42 am

Re: Can't connect to terminal "Socket Close"

Unread post by astropixel » Fri Dec 08, 2017 10:33 am

ismithers wrote:
BreizhCat wrote:Hello

I had the same issue on my docker.
I remove the file(s) in

Code: Select all

/var/lib/docker/network/files/
After that, i had access back to the terminal.

Hope it can help !

Yann
Hey Yann, thanks for the post however this doesn't resolve it for me. The files directory appears as soon as I start Docker again, and then I get Socket Close.
Sorry for resurrecting an old post, but I'm having the same issue. Each time I try to use the terminal in Docker, I get the error 'Socket Closed'.
I've restarted DSM, but I could not find the location to delete the folder

Any ideas?

Post Reply

Return to “Docker”