ScanSkill

docker compose pull

docker compose pull is used to pull service images defined in compose.yaml file, but it doesn't start containers based on those images.

Syntax

$ docker compose pull [options] [SERVICE...]

Here,

OPTIONS:

  • --ignore-pull-failures → Pull what it can and ignore images with pull failures
  • --include-deps → Also pull services, declared as dependencies
  • --no-parallel → disable parallel pulling (Deprecated)
  • --parallel → enable parallel pulling (Deprecated)
  • --quiet , -q → pull without printing progress information

Example

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

Here, if you run docker compose pull ServiceName, docker pulls the associated image. In this, if you run docker compose pull db following will be output:

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

ss