Why Do I Keep Getting ‘Interrupted’ Messages When Using Docker Compose Pull?

0
95
Asked By CuriousCoder42 On

I've been running into an issue where doing a `docker compose pull` results in several 'Interrupted' messages. For instance, while pulling images from the containers, some like 'mqtt', 'novnc', and 'vaultwarden' repeatedly show this error. However, when I pull each image individually using a command that combines `docker compose config --services` and `xargs`, everything works perfectly with no issues. I've updated to the latest Docker Compose version (v2.38.1) but I'm still encountering this problem on Ubuntu 24.04.2 LTS. Any insights on why this might be happening?

4 Answers

Answered By ImageEnthusiast On

Honestly, I don't get why you'd want all those services in one compose file. Seems like a lot to manage. But if it works for you, more power to ya! Just remember that if you're pulling them all at once, it might slow things down or lead to interruptions.

CuriousCoder42 -

It's actually organized into a few separate ones, but I prefer managing everything from a single main one for ease of updates.

Answered By DevOpsNinja On

Interesting problem! I haven't encountered the 'Interrupted' message before, but given that pulling works fine when done one by one, it could be that Docker Hub's rate limits are kicking in depending on how frequently you pull images. Just a thought! Good luck!

Answered By TechWhiz101 On

Using a single compose file for many services can time out during pulls, especially if there are a lot of images. Docker Compose has a timeout period (around 60 seconds by default). You might want to try increasing this timeout using the `COMPOSE_HTTP_TIMEOUT` environment variable like so: `COMPOSE_HTTP_TIMEOUT=300 docker-compose pull` if you’re using v1, otherwise double-check your current setup as you mentioned using v2.

CuriousCoder42 -

That makes sense! I wasn’t aware of the timeout. I’ll give your solution a shot.

Answered By DockerDude27 On

This could be due to running different versions of Docker Compose and the Docker engine. Check to make sure both are updated to avoid any compatibility issues. Sometimes mixing versions can lead to unexpected behaviors. Glad to hear you're already on the latest for Compose!

CuriousCoder42 -

Updating Docker Engine seems to have resolved the issue! Thanks for the suggestion!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.