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.

Docker containers startup extremely slow

Featured Replies

I hadn't rebooted in 5 months, so without changing any settings I did today. Ever since then Docker has been really slow to start up. I have about 40 containers and it takes 20 minutes to load them all. This is new behaviour. Previously everything was started in 3-5 minutes. After having watched it load all the containers, it looks like Docker starts every container one by one, instead of all at the same time.

Is this new? Can I change this back to it's previous setting somehow? I can speed it up by manually starting the containers, but that's tedious work.

Things I've tried:

  • Updating from 7.3.0 to 7.3.3

  • Updating all the plugins

  • Booting with Docker off, and manually starting it.

  • Community Expert

Docker appears to be working normally to me. Each container starts in about a second, but several of them have an autostart wait set:

- 120 seconds: Czkawka, OpenSpeedTest, DiskSpeed, qdirstat and ollama

- 60 seconds: karakeep, pgadmin4, RedisInsight, heimdall and Norish

- 30 seconds: tautulli

When a container has a wait, Unraid waits that many seconds before starting the next container in the list. Those waits add up to about 15.5 minutes, and that is almost all of the time it takes. Autostart has always started containers one at a time in the order shown. The waits are meant for containers that others depend on, for example a database that must be up before the app that uses it. With no waits, 40 containers start in under a minute. My guess is that these waits were added since your last reboot 5 months ago, so this was the first boot where they were used.

To fix it, go to the Docker page and switch to Advanced View. In the autostart column, clear the wait value (or set it to 0) for every container that nothing else needs to wait for. If an app does need its database or Redis first, put the database above the app in the autostart order and give it a short wait, like 10 to 15 seconds. That should bring startup back to a minute or two.

  • Author

Ok so if I understand you correctly, if I set one container to 120s wait, all the containers below it also wait 120s?

1 hour ago, BreakfastPurrito said:

Ok so if I understand you correctly, if I set one container to 120s wait, all the containers below it also wait 120s?

Yes

  • Author

Dear lord. I assumed that all containers started at the same time, and that the timers ran consecutively.

Does that mean that the order in which they appear from top to bottom on the Docker page is also the order in which they start?

3 minutes ago, BreakfastPurrito said:

Dear lord. I assumed that all containers started at the same time, and that the timers ran consecutively.

Does that mean that the order in which they appear from top to bottom on the Docker page is also the order in which they start?

Yes

You can reorder them by clicking the green padlock and dragging them to the desired position.

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...

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.