Docker CLI

repository·master·Indexed 26 days ago

https://github.com/docker/cli

The command-line interface for interacting with the Docker engine. This repository contains the source code and build definitions for the CLI, including documentation on building from source, enabling experimental features, testing OpenTelemetry (OTEL) functionality, and managing the Docker API client and contexts.

Tokens
173K
Snippets
418
Records
1.1K
Agent score
90%

What's inside docker-cli

  1. Understand Virtual Machines (VMs) vs Containers

    master

    A virtual machine (VM) emulates a complete computer and imitates dedicated hardware, isolating an entire operating system.

    Key differences from containers:

    • Weight: VMs are heavier to run than containers.
    • Isolation: VMs provide more isolation.
    • Resources: VMs receive their own dedicated set of resources and perform minimal sharing compared to the shared resource model of containers.
  2. Access Docker Engine documentation and references

    master

    The Docker Engine reference documentation is split into several key areas depending on your task:

    • Dockerfile syntax and instructions: Use the Dockerfile reference to learn how to build images.
    • Container execution: Refer to the Docker run reference for detailed information on the docker run command and its flags.
    • CLI Commands: Use the Command line reference to find all available Docker CLI commands.
    • Engine API: For programmatic interaction with the Docker Engine, use the API Reference.
  3. Manage Swarm services with the docker service command

    master

    The docker service command is used to manage services within a Docker Swarm cluster.

    Important: This is a cluster management command and must be executed on a swarm manager node. It will not work on worker nodes or standalone Docker engines that are not part of a swarm.

  4. Deprecated Docker Engine features overview

    master
    This document tracks the deprecation and removal of various Docker Engine features. A feature marked as Deprecated is still functional but scheduled for removal in a future version. A feature marked as Removed is no longer available in the specified version. Use this list to audit your workflows, scripts, and Dockerfiles for upcoming breaking changes.
  5. Understand Docker feature deprecation and removal status

    master

    Docker uses specific terminology to indicate the lifecycle status of engine features. When planning migrations or evaluating feature stability, note the following definitions:

    • Deprecated: The feature is marked as deprecated and should no longer be used. It may be removed, disabled, or have its behavior changed in a future release. The deprecation release and the tentative removal release are tracked in the deprecation documentation.
    • Removed: The feature has been removed, disabled, or hidden.
    • Soft Deprecated: A subset of deprecated features that remain functional for backward compatibility to allow for migration. Using these features may trigger warnings, but they still work. Users should migrate to the recommended alternatives as soon as possible.
  6. Manage Swarm secrets with the docker secret command

    master
    The docker secret command is used to manage Swarm secrets. Secrets allow you to store sensitive data (such as passwords, SSL certificates, or API keys) securely in the Swarm cluster. These secrets can then be mounted into services as files in the /run/secrets/ directory within the container.