Différences

Ci-dessous, les différences entre deux révisions de la page.

--- start:linux:debian:astuces [2026/02/04 04:11] – admin
+++ start:linux:debian:astuces [2026/02/04 04:35] (Version actuelle) – admin
@@ Ligne 106: / Ligne 106: @@
   * Niveau requis : {{tag>débutant avisé}}
   * Commentaires : Docker.io est un outil permettant de créer facilement des conteneurs pour certaines applications.
-  * Débutant, à savoir : [[:doc:systeme:commandes:le_debianiste_qui_papillonne|Utiliser GNU/Linux en ligne de commande, tout commence là !.]] :-)
+  * Débutant, à savoir : [[https://debian-facile.org/doc:systeme:commandes:le_debianiste_qui_papillonne|Utiliser GNU/Linux en ligne de commande, tout commence là !.]] :-)
-  * Suivi : {{tag>à-tester}}
+    * Création par [[https://debian-facile.org/utilisateurs:captnfab|captnfab]] 13/08/2023
-    * Création par [[user>captnfab]] 13/08/2023
     * Testé par <...> le <...> FIXME
   * Commentaires sur le forum : [[https://debian-facile.org/viewtopic.php?pid=402085#p402085 | Lien vers le forum concernant ce tuto]] ((N'hésitez pas à y faire part de vos remarques, succès, améliorations ou échecs !))
@@ Ligne 141: / Ligne 140: @@
 </code>
-À noter qu'il faut ensuite redémarrer, fermer la session ou taper ''newgrp docker'' pour que le shell hérite des bons droits, cf [[:doc:systeme:droit-rajouter-un-utilisateur-a-un-groupe|Ajouter un utilisateur à un groupe]]
+À noter qu'il faut ensuite redémarrer, fermer la session ou taper ''newgrp docker'' pour que le shell hérite des bons droits, cf [[https://debian-facile.org/doc:systeme:droit-rajouter-un-utilisateur-a-un-groupe|Ajouter un utilisateur à un groupe]]
 ==== Construire un conteneur ====
@@ Ligne 244: / Ligne 243: @@
         permission denied</code>
-Le shell utilisé pour lancer la commande ne dispose pas des droits suffisants. S'assurer d'avoir bien suivi le paragraphe Permissions et lu [[:doc:systeme:droit-rajouter-un-utilisateur-a-un-groupe|Ajouter un utilisateur à un groupe]].
+Le shell utilisé pour lancer la commande ne dispose pas des droits suffisants. S'assurer d'avoir bien suivi le paragraphe Permissions et lu [[https://debian-facile.org/doc:systeme:droit-rajouter-un-utilisateur-a-un-groupe|Ajouter un utilisateur à un groupe]].
+[[https://docs.docker.com/engine/install/debian/|Debian Docker ]]
+<markdown>
+# Install Docker Engine on Debian
+To get started with Docker Engine on Debian, make sure you
+[meet the prerequisites](#prerequisites), and then follow the
+[installation steps](#installation-methods).
+## Prerequisites
+### Firewall limitations
+> [!WARNING]
+>
+> Before you install Docker, make sure you consider the following
+> security implications and firewall incompatibilities.
+- If you use ufw or firewalld to manage firewall settings, be aware that
+  when you expose container ports using Docker, these ports bypass your
+  firewall rules. For more information, refer to
+  [Docker and ufw](/engine/network/packet-filtering-firewalls/#docker-and-ufw).
+- Docker is only compatible with `iptables-nft` and `iptables-legacy`.
+  Firewall rules created with `nft` are not supported on a system with Docker installed.
+  Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
+  and that you add them to the `DOCKER-USER` chain,
+  see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls/).
+### OS requirements
+To install Docker Engine, you need one of these Debian versions:
+- Debian Trixie 13 (stable)
+- Debian Bookworm 12 (oldstable)
+- Debian Bullseye 11 (oldoldstable)
+Docker Engine for Debian is compatible with x86_64 (or amd64), armhf (arm/v7),
+arm64, and ppc64le (ppc64el) architectures.
+### Uninstall old versions
+Before you can install Docker Engine, you need to uninstall any conflicting packages.
+Your Linux distribution may provide unofficial Docker packages, which may conflict
+with the official packages provided by Docker. You must uninstall these packages
+before you install the official version of Docker Engine.
+The unofficial packages to uninstall are:
+- `docker.io`
+- `docker-compose`
+- `docker-doc`
+- `podman-docker`
+Moreover, Docker Engine depends on `containerd` and `runc`. Docker Engine
+bundles these dependencies as one bundle: `containerd.io`. If you have
+installed the `containerd` or `runc` previously, uninstall them to avoid
+conflicts with the versions bundled with Docker Engine.
+Run the following command to uninstall all conflicting packages:
+```console
+$ sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-doc podman-docker containerd runc | cut -f1)
+```
+`apt` might report that you have none of these packages installed.
+Images, containers, volumes, and networks stored in `/var/lib/docker/` aren't
+automatically removed when you uninstall Docker. If you want to start with a
+clean installation, and prefer to clean up any existing data, read the
+[uninstall Docker Engine](#uninstall-docker-engine) section.
+## Installation methods
+You can install Docker Engine in different ways, depending on your needs:
+- Docker Engine comes bundled with
+  [Docker Desktop for Linux](/desktop/setup/install/linux/). This is
+  the easiest and quickest way to get started.
+- Set up and install Docker Engine from
+  [Docker's `apt` repository](#install-using-the-repository).
+- [Install it manually](#install-from-a-package) and manage upgrades manually.
+- Use a [convenience script](#install-using-the-convenience-script). Only
+  recommended for testing and development environments.
+Apache License, Version 2.0. See [LICENSE](https://github.com/moby/moby/blob/master/LICENSE) for the full license.
+### Install using the `apt` repository {#install-using-the-repository}
+Before you install Docker Engine for the first time on a new host machine, you
+need to set up the Docker `apt` repository. Afterward, you can install and update
+Docker from the repository.
+. Set up Docker's `apt` repository.
+   ```bash
+   # Add Docker's official GPG key:
+   sudo apt update
+   sudo apt install ca-certificates curl
+   sudo install -m 0755 -d /etc/apt/keyrings
+   sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
+   sudo chmod a+r /etc/apt/keyrings/docker.asc
+   # Add the repository to Apt sources:
+   sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
+   Types: deb
+   URIs: https://download.docker.com/linux/debian
+   Suites: $(. /etc/os-release && echo "$VERSION_CODENAME")
+   Components: stable
+   Signed-By: /etc/apt/keyrings/docker.asc
+   EOF
+   sudo apt update
+   ```
+   > [!NOTE]
+   >
+   > If you use a derivative distribution, such as Kali Linux,
+   > you may need to substitute the part of this command that's expected to
+   > print the version codename:
+   >
+   > ```console
+   > $(. /etc/os-release && echo "$VERSION_CODENAME")
+   > ```
+   >
+   > Replace this part with the codename of the corresponding Debian release,
+   > such as `bookworm`.
+. Install the Docker packages.
+Latest
+   To install the latest version, run:
+   ```console
+   $ sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
+   ```
+   **Specific version**
+   To install a specific version of Docker Engine, start by listing the
+   available versions in the repository:
+   ```console
+   $ apt list --all-versions docker-ce
+   docker-ce/bookworm 5:29.2.1-1~debian.12~bookworm <arch>
+   docker-ce/bookworm 5:29.2.0-1~debian.12~bookworm <arch>
+   ...
+   ```
+   Select the desired version and install:
+   ```console
+   $ VERSION_STRING=5:29.2.1-1~debian.12~bookworm
+   $ sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
+   ```
+    > [!NOTE]
+    >
+    > The Docker service starts automatically after installation. To verify that
+    > Docker is running, use:
+    >
+    > ```console
+    > $ sudo systemctl status docker
+    > ```
+    >
+    > Some systems may have this behavior disabled and will require a manual start:
+    >
+    > ```console
+    > $ sudo systemctl start docker
+    > ```
+. Verify that the installation is successful by running the `hello-world` image:
+   ```console
+   $ sudo docker run hello-world
+   ```
+   This command downloads a test image and runs it in a container. When the
+   container runs, it prints a confirmation message and exits.
+You have now successfully installed and started Docker Engine.
+> [!TIP]
+>
+> Receiving errors when trying to run without root?
+>
+> The `docker` user group exists but contains no users, which is why you’re required
+> to use `sudo` to run Docker commands. Continue to [Linux postinstall](/engine/install/linux-postinstall)
+> to allow non-privileged users to run Docker commands and for other optional configuration steps.
+#### Upgrade Docker Engine
+To upgrade Docker Engine, follow step 2 of the
+[installation instructions](#install-using-the-repository),
+choosing the new version you want to install.
+### Install from a package
+If you can't use Docker's `apt` repository to install Docker Engine, you can
+download the `deb` file for your release and install it manually. You need to
+download a new file each time you want to upgrade Docker Engine.
+<!-- markdownlint-disable-next-line -->
+. Go to [`https://download.docker.com/linux/debian/dists/`](https://download.docker.com/linux/debian/dists/).
+. Select your Debian version in the list.
+. Go to `pool/stable/` and select the applicable architecture (`amd64`,
+   `armhf`, `arm64`, or `s390x`).
+. Download the following `deb` files for the Docker Engine, CLI, containerd,
+   and Docker Compose packages:
+   - `containerd.io_<version>_<arch>.deb`
+   - `docker-ce_<version>_<arch>.deb`
+   - `docker-ce-cli_<version>_<arch>.deb`
+   - `docker-buildx-plugin_<version>_<arch>.deb`
+   - `docker-compose-plugin_<version>_<arch>.deb`
+. Install the `.deb` packages. Update the paths in the following example to
+   where you downloaded the Docker packages.
+   ```console
+   $ sudo dpkg -i ./containerd.io_<version>_<arch>.deb \
+     ./docker-ce_<version>_<arch>.deb \
+     ./docker-ce-cli_<version>_<arch>.deb \
+     ./docker-buildx-plugin_<version>_<arch>.deb \
+     ./docker-compose-plugin_<version>_<arch>.deb
+   ```
+    > [!NOTE]
+    >
+    > The Docker service starts automatically after installation. To verify that
+    > Docker is running, use:
+    >
+    > ```console
+    > $ sudo systemctl status docker
+    > ```
+    >
+    > Some systems may have this behavior disabled and will require a manual start:
+    >
+    > ```console
+    > $ sudo systemctl start docker
+    > ```
+. Verify that the installation is successful by running the `hello-world` image:
+   ```console
+   $ sudo docker run hello-world
+   ```
+   This command downloads a test image and runs it in a container. When the
+   container runs, it prints a confirmation message and exits.
+You have now successfully installed and started Docker Engine.
+> [!TIP]
+>
+> Receiving errors when trying to run without root?
+>
+> The `docker` user group exists but contains no users, which is why you’re required
+> to use `sudo` to run Docker commands. Continue to [Linux postinstall](/engine/install/linux-postinstall)
+> to allow non-privileged users to run Docker commands and for other optional configuration steps.
+#### Upgrade Docker Engine
+To upgrade Docker Engine, download the newer package files and repeat the
+[installation procedure](https://docs.docker.com/engine/install/debian/#install-from-a-package), pointing to the new files.
+### Install using the convenience script
+Docker provides a convenience script at
+[https://get.docker.com/](https://get.docker.com/) to install Docker into
+development environments non-interactively. The convenience script isn't
+recommended for production environments, but it's useful for creating a
+provisioning script tailored to your needs. Also refer to the
+[install using the repository](#install-using-the-repository) steps to learn
+about installation steps to install using the package repository. The source code
+for the script is open source, and you can find it in the
+[`docker-install` repository on GitHub](https://github.com/docker/docker-install).
+<!-- prettier-ignore -->
+Always examine scripts downloaded from the internet before running them locally.
+Before installing, make yourself familiar with potential risks and limitations
+of the convenience script:
+- The script requires `root` or `sudo` privileges to run.
+- The script attempts to detect your Linux distribution and version and
+  configure your package management system for you.
+- The script doesn't allow you to customize most installation parameters.
+- The script installs dependencies and recommendations without asking for
+  confirmation. This may install a large number of packages, depending on the
+  current configuration of your host machine.
+- By default, the script installs the latest stable release of Docker,
+  containerd, and runc. When using this script to provision a machine, this may
+  result in unexpected major version upgrades of Docker. Always test upgrades in
+  a test environment before deploying to your production systems.
+- The script isn't designed to upgrade an existing Docker installation. When
+  using the script to update an existing installation, dependencies may not be
+  updated to the expected version, resulting in outdated versions.
+> [!TIP]
+>
+> Preview script steps before running. You can run the script with the `--dry-run` option to learn what steps the
+> script will run when invoked:
+>
+> ```console
+> $ curl -fsSL https://get.docker.com -o get-docker.sh
+> $ sudo sh ./get-docker.sh --dry-run
+> ```
+This example downloads the script from
+[https://get.docker.com/](https://get.docker.com/) and runs it to install the
+latest stable release of Docker on Linux:
+```console
+$ curl -fsSL https://get.docker.com -o get-docker.sh
+$ sudo sh get-docker.sh
+Executing docker install script, commit: 7cae5f8b0decc17d6571f9f52eb840fbc13b2737
+<...>
+```
+You have now successfully installed and started Docker Engine. The `docker`
+service starts automatically on Debian based distributions. On `RPM` based
+distributions, such as CentOS, Fedora or RHEL, you need to start it
+manually using the appropriate `systemctl` or `service` command. As the message
+indicates, non-root users can't run Docker commands by default.
+> **Use Docker as a non-privileged user, or install in rootless mode?**
+>
+> The installation script requires `root` or `sudo` privileges to install and
+> use Docker. If you want to grant non-root users access to Docker, refer to the
+> [post-installation steps for Linux](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user).
+> You can also install Docker without `root` privileges, or configured to run in
+> rootless mode. For instructions on running Docker in rootless mode, refer to
+> [run the Docker daemon as a non-root user (rootless mode)](https://docs.docker.com/engine/security/rootless/).
+#### Install pre-releases
+Docker also provides a convenience script at
+[https://test.docker.com/](https://test.docker.com/) to install pre-releases of
+Docker on Linux. This script is equal to the script at `get.docker.com`, but
+configures your package manager to use the test channel of the Docker package
+repository. The test channel includes both stable and pre-releases (beta
+versions, release-candidates) of Docker. Use this script to get early access to
+new releases, and to evaluate them in a testing environment before they're
+released as stable.
+To install the latest version of Docker on Linux from the test channel, run:
+```console
+$ curl -fsSL https://test.docker.com -o test-docker.sh
+$ sudo sh test-docker.sh
+```
+#### Upgrade Docker after using the convenience script
+If you installed Docker using the convenience script, you should upgrade Docker
+using your package manager directly. There's no advantage to re-running the
+convenience script. Re-running it can cause issues if it attempts to re-install
+repositories which already exist on the host machine.
+## Uninstall Docker Engine
+. Uninstall the Docker Engine, CLI, containerd, and Docker Compose packages:
+   ```console
+   $ sudo apt purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
+   ```
+. Images, containers, volumes, or custom configuration files on your host
+   aren't automatically removed. To delete all images, containers, and volumes:
+   ```console
+   $ sudo rm -rf /var/lib/docker
+   $ sudo rm -rf /var/lib/containerd
+   ```
+. Remove source list and keyrings
+   ```console
+   $ sudo rm /etc/apt/sources.list.d/docker.sources
+   $ sudo rm /etc/apt/keyrings/docker.asc
+   ```
+You have to delete any edited configuration files manually.
+## Next steps
+- Continue to [Post-installation steps for Linux](https://docs.docker.com/engine/install/linux-postinstall/).
+</markdown>