DOCKER-COMPOSE-PULL(1)

πŸ“¦ version 2.26.1, in debian trixie

πŸ’… docker-compose-pull(1) β€” the docker-compose-pull manual, bestie edition πŸŽ€

okay so you opened the manual for docker-compose-pull and honestly? slay. it's giving "I want my images and I want them now". let's get into it ✨

✨ NAME ✨

docker-compose-pull β€” pull service images 🫢

✨ SYNOPSIS ✨

docker compose pull [OPTIONS] [SERVICE...]

✨ DESCRIPTION ✨

So here's the vibe: this pulls an image that's associated with a service defined in a compose.yaml file. That's it. That's the whole thing.

BUT. It does not start containers based on those images. It's just the pulling. The container-starting is somebody else's job, bestie. no cap. πŸ™ˆ

✨ OPTIONS ✨

  • -h, --help[=false] β€” help for pull πŸ’–
  • --ignore-buildable[=false] β€” Ignore images that can be built
  • --ignore-pull-failures[=false] β€” Pull what it can and ignores images with pull failures
  • --include-deps[=false] β€” Also pull services declared as dependencies πŸ‘‘
  • --policy="" β€” Apply pull policy ("missing"|"always")
  • -q, --quiet[=false] β€” Pull without printing progress information 🀫

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

these ones come from the parent command, so they're not technically yours but they're here and they're iconic:

  • --dry-run[=false] β€” Execute command in dry run mode 🌈

✨ EXAMPLE ✨

okay consider the following compose.yaml, fr fr:

services:
  db:
    image: postgres
  web:
    build: .
    command: bundle exec rails s -p 3000 -b '0.0.0.0'
    volumes:
      - .:/myapp
    ports:
      - "3000:3000"
    depends_on:
      - db

If you run docker compose pull ServiceName in the same directory as the compose.yaml file that defines the service, Docker pulls the associated image. For example, to call the postgres image configured as the db service in our example, you would run docker compose pull db. 🐘

$ docker compose pull db
[+] Running 1/15
 β Έ db Pulling                                                             12.4s
   β Ώ 45b42c59be33 Already exists                                           0.0s
   β Ή 40adec129f1a Downloading  3.374MB/4.178MB                             9.3s
   β Ή b4c431d00c78 Download complete                                        9.3s
   β Ή 2696974e2815 Download complete                                        9.3s
   β Ή 564b77596399 Downloading  5.622MB/7.965MB                             9.3s
   β Ή 5044045cf6f2 Downloading  216.7kB/391.1kB                             9.3s
   β Ή d736e67e6ac3 Waiting                                                  9.3s
   β Ή 390c1c9a5ae4 Waiting                                                  9.3s
   β Ή c0e62f172284 Waiting                                                  9.3s
   β Ή ebcdc659c5bf Waiting                                                  9.3s
   β Ή 29be22cb3acc Waiting                                                  9.3s
   β Ή f63c47038e66 Waiting                                                  9.3s
   β Ή 77a0c198cde5 Waiting                                                  9.3s
   β Ή c8752d5b785c Waiting                                                  9.3s

docker compose pull tries to pull image for services with a build section. If pull fails, it lets you know this service image must be built. You can skip this by setting --ignore-buildable flag. πŸ’€ (the original example ends with a dangling ``` fence, so like… consider this your official heads up that the code block formatting there is a lil unhinged πŸ™ˆ)

✨ SEE ALSO ✨

and that's the whole manual, bestie!! this page is from Mar 2025, and it's the DOCKER-COMPOSE-PULL(1) page in the docker-compose-pull manual set. go pull something cute. πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from