Can't Kill Tranmission Docker. Forcing me to hard shutdown the server


Recommended Posts

Transmission becomes unresponsive(last time was after I ran "delete local data"). I can't stop or kill the docker container. Stopping the docker service doesn't cause the container to stop either(disabling docker in settings). I've tried deleting the docker vdisk img and starting from scratch and I'm getting the same issues. Trying to stop or shutdown the array causes the server to hang. I have to hard shutdown the server using the power button. 

 

What on earth could be causing this?

It's not an Intel NUC despite the diagnostic name. 

nuc-diagnostics-20210518-1203.zip

 

 

Whenever I try and get into the container I get the following error: 
 

root@nuc:~# docker exec -it transmission bash
OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: process_linux.go:112: executing setns process caused: exit status 1: unknown

 

Edited by Fierce Waffle
Link to comment
7 minutes ago, jonathanm said:

Which transmission container are you talking about? There are individual support threads for each version, since you are doing things in a non-standard way you will need to manually figure out which thread to post in.

Gotcha. I'm currently using `haugene/transmission-openvpn`

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.