Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

How can I kill a docker I can't see

Featured Replies

I installed the filebot docker and now I have this:

 

How can I kill the container?

Docker_Upset.jpg.d8a1600e88bd8adb9898ab50090dc4b7.jpg

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?

Failing that, post the results of

docker ps -a

and

docker images

  • Author

Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot.  :o

 

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.

 

 

Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot.  :o

 

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?

  • Author

Thanks, I rebuilt all of the containers, which worked well, except CouchPotato. Apparently CouchPotato was cohabiting with FileBot.  :o

 

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.

CP_Error.jpg.3484e0e33a872de87973198957aabfe7.jpg

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.