Docker Config Reference (push / pull)

Examples of Using the Docker Pull Command

docker pull nginx:latest

This command retrieves the most recent version of the Nginx web server image from Docker Hub, the default registry. It downloads all necessary layers, including the base operating system and application components, ensuring the image is available locally for container instantiation. This approach is particularly useful for initiating web server deployments, as it automatically selects the latest stable release while verifying integrity through layer digests.

docker pull ubuntu:20.04

This command downloads a specific version of the Ubuntu image, tagged as 20.04, from Docker Hub. By specifying the tag, it guarantees compatibility with long-term support requirements, fetching only the designated layers without pulling unrelated variants. This is essential for reproducible builds in development environments, where precise OS versions are critical for dependency management.

docker pull --platform linux/arm64 golang:1.21

Utilizing the --platform flag, this command pulls the Golang 1.21 image optimized for the ARM64 architecture from Docker Hub. It overrides the default host platform detection, enabling cross-architecture compatibility for edge devices or heterogeneous clusters. This facilitates efficient compilation and runtime for Go applications on non-standard hardware.

docker pull mysql:8.0 --quiet

The --quiet flag suppresses progress output during the download of the MySQL 8.0 image from Docker Hub, displaying only essential information. This minimizes console clutter in automated scripts or CI/CD pipelines, while still ensuring the relational database image is fetched with all required layers for database container operations.

docker pull --all-tags redis

This command downloads all available tags of the Redis image from Docker Hub, encompassing various versions and variants. It is advantageous for comprehensive local caching or testing multiple iterations, though it consumes significant storage and bandwidth, making it suitable for archival or evaluation purposes in controlled settings.

Examples of Using the Docker Push Command

docker push myrepo/myimage:latest

This command uploads the locally built image tagged as "myrepo/myimage:latest" to a specified repository on Docker Hub or a private registry. It transfers all image layers and manifest, enabling distribution for team collaboration or deployment. Authentication is required if the repository is private, ensuring secure sharing of custom applications.

docker push --all-tags myrepo/customapp

Employing the --all-tags flag, this command pushes every tagged variant of the "myrepo/customapp" image to the registry. It supports versioning strategies by uploading multiple iterations simultaneously, facilitating rollback options or multi-environment support without repeated individual pushes.

docker push myrepo/webserver:1.0 --quiet

The --quiet option limits output to critical messages while uploading the "myrepo/webserver:1.0" image to the registry. This is beneficial in scripted environments to reduce logging noise, while the specific tag ensures precise version control for web server distributions.

docker push --disable-content-trust myrepo/secureimage:latest

This command pushes the "myrepo/secureimage:latest" image while disabling content trust verification, bypassing signature checks for expedited uploads in trusted networks. It is used cautiously in development phases but not recommended for production to maintain image integrity against tampering.

docker push registry.example.com/private/image:dev

This command uploads the "private/image:dev" image to a custom registry at "registry.example.com". It specifies an alternative endpoint for private deployments, requiring prior login for authentication, and supports internal enterprise distributions where Docker Hub is not utilized.