March 27, 201610 yr I installed the filebot docker and now I have this: How can I kill the container?
March 28, 201610 yr I installed the filebot docker and now I have this: How can I kill the container? Weird. Have you tried stopping and starting the docker service? Settings>Docker>Enable Docker:>No>Apply then Settings>Docker>Enable Docker:>Yes>Apply OR via the CLI /etc/rc.d/rc.docker restart Then go back into the Docker Tab and see what happens then?
March 28, 201610 yr Author Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot. So I ended up with two CouchPotato containers, except one wasn't really CouchPotato, as I could not kill it by name. But I could see it's ID on the screen, so I killed it from the CLI. Then recreated the real CP. Everything seems OK now.
March 28, 201610 yr Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot. So I ended up with two CouchPotato containers, except one wasn't really CouchPotato, as I could not kill it by name. But I could see it's ID on the screen, so I killed it from the CLI. Then recreated the real CP. Everything seems OK now. Really? That seems REALLY weird. Did you happen to capture any screenshots / information showing this? Can you post a syslog for future reference / bug reporting?
March 28, 201610 yr Author Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot. So I ended up with two CouchPotato containers, except one wasn't really CouchPotato, as I could not kill it by name. But I could see it's ID on the screen, so I killed it from the CLI. Then recreated the real CP. Everything seems OK now. Really? That seems REALLY weird. Did you happen to capture any screenshots / information showing this? Can you post a syslog for future reference / bug reporting? Other than the picture I posted with the Docker error, I have a picture of the container error. But I did not take a picture of the two CP containers. I don't think I selected a proper template so that's what caused the issue. It was container e423...... that I killed from the CLI.
Archived
This topic is now archived and is closed to further replies.