Install Docker Engine On Ubuntu
- Get started
- Guides
- Reference
- Docker Engine
- Install
- Ubuntu
- Debian
- RHEL
- Fedora
- Raspberry Pi OS (32-bit / armhf)
- CentOS
- SLES (s390x)
- Binaries
- Post-installation steps
- Storage
- Volumes
- Bind mounts
- tmpfs mounts
- Storage drivers
- Select a storage driver
- BTRFS storage driver
- Device Mapper storage driver (deprecated)
- OverlayFS storage driver
- VFS storage driver
- windowsfilter storage driver
- ZFS storage driver
- containerd image store
- Networking
- Docker with iptables
- Docker with nftables
- Packet filtering and firewalls
- Port publishing and mapping
- Network drivers
- Bridge network driver
- Host network driver
- IPvlan network driver
- Macvlan network driver
- None network driver
- Overlay network driver
- CA certificates
- Legacy container links
- Containers
- Start containers automatically
- Run multiple processes in a container
- Resource constraints
- Runtime metrics
- Running containers
- CLI
- Completion
- Proxy configuration
- Filter commands
- Format command and log output
- OpenTelemetry for the Docker CLI
- Daemon
- Start the daemon
- Use IPv6 networking
- Daemon proxy configuration
- Live restore
- Alternative container runtimes
- Collect Docker metrics with Prometheus
- Configure remote access for Docker daemon
- Read the daemon logs
- Troubleshooting the Docker daemon
- Manage resources
- Docker contexts
- Docker object labels
- Prune unused Docker objects
- Logs and metrics
- Configure logging drivers
- Customize log driver output
- Logging drivers
- Amazon CloudWatch Logs logging driver
- ETW logging driver
- Fluentd logging driver
- Google Cloud Logging driver
- Graylog Extended Format logging driver
- Journald logging driver
- JSON File logging driver
- Local file logging driver
- Splunk logging driver
- Syslog logging driver
- Use a logging driver plugin
- Use docker logs with remote logging drivers
- Security
- Rootless mode
- Tips
- Troubleshooting
- Antivirus software and Docker
- AppArmor security profiles for Docker
- Content trust in Docker
- Automation with content trust
- Delegations for content trust
- Deploy Notary Server with Compose
- Manage keys for content trust
- Play in a content trust sandbox
- Docker security non-events
- Isolate containers with a user namespace
- Protect the Docker daemon socket
- Seccomp security profiles for Docker
- Verify repository client with certificates
- Rootless mode
- Swarm mode
- Administer and maintain a swarm of Docker Engines
- Deploy a stack to a swarm
- Deploy services to a swarm
- Getting started with Swarm mode
- Create a swarm
- Add nodes to the swarm
- Deploy a service to the swarm
- Inspect a service on the swarm
- Scale the service in the swarm
- Delete the service running on the swarm
- Apply rolling updates to a service
- Drain a node on the swarm
- How swarm works
- How nodes work
- How services work
- Manage swarm security with public key infrastructure (PKI)
- Swarm task states
- Join nodes to a swarm
- Lock your swarm to protect its encryption key
- Manage nodes in a swarm
- Manage sensitive data with Docker secrets
- Manage swarm service networks
- Raft consensus in swarm mode
- Run Docker Engine in swarm mode
- Store configuration data using Docker Configs
- Swarm mode key concepts
- Use Swarm mode routing mesh
- Deprecated features
- Docker Engine plugins
- Access authorization plugin
- Docker log driver plugins
- Docker network driver plugins
- Docker Plugin API
- Docker volume plugins
- Plugin Config Version 1 of Plugin V2
- Use Docker Engine plugins
- Release notes
- Engine v29
- Engine v28
- Engine v27
- Engine v26.1
- Engine v26.0
- Engine v25.0
- Engine v24.0
- Engine v23.0
- Engine v20.10
- Engine v19.03
- Engine v18.09
- Engine v18.06
- Engine v18.05
- Engine v18.04
- Engine v18.03
- Engine v18.02
- Engine v18.01
- Engine v17.12
- Engine v17.11
- Engine v17.10
- Engine v17.09
- Engine v17.07
- Engine v17.06
- Engine v17.05
- Engine v17.04
- Engine v17.03
- Prior releases
- Install
- Docker Build
- Core concepts
- Docker Build Overview
- Dockerfile overview
- Build context
- Building
- Multi-stage
- Variables
- Secrets
- Multi-platform
- Export binaries
- Container Device Interface (CDI)
- Best practices
- Base images
- Build checks New
- Builders
- Build drivers
- Docker container driver
- Docker driver
- Kubernetes driver
- Remote driver
- Manage builders
- Build drivers
- Bake
- Introduction
- Targets
- Inheritance
- Variables
- Expressions
- Functions
- Matrix targets
- Contexts
- Bake file reference
- Bake standard library functions
- Building with Bake from a Compose file
- Overriding configurations
- Remote Bake file definition
- Cache
- Build cache invalidation
- Build garbage collection
- Cache storage backends
- Amazon S3 cache
- Azure Blob Storage cache
- GitHub Actions cache
- Inline cache
- Local cache
- Registry cache
- Optimize cache usage in builds
- CI
- GitHub Actions
- Annotations
- Attestations
- Build checks
- Build secrets
- Build summary
- BuildKit configuration
- Cache management
- Copy image between registries
- Export to Docker
- Local registry
- Multi-platform image
- Named contexts
- Push to multiple registries
- Reproducible builds
- Share image between jobs
- Tags and labels
- Test before push
- Update Docker Hub description
- GitHub Actions
- Metadata
- Annotations
- Build attestations
- Image attestation storage
- Provenance attestations
- SBOM attestations
- SLSA definitions
- Exporters
- Image and registry exporters
- Local and tar exporters
- OCI and Docker exporters
- BuildKit
- buildkitd.toml
- Configure BuildKit
- Custom Dockerfile syntax
- Dockerfile release notes
- Debugging
- OpenTelemetry support
- Build release notes
- Core concepts
- Docker Compose
- Introduction to Compose
- How Compose works
- Why use Compose?
- History and development
- Install
- Plugin
- Standalone (Legacy)
- Uninstall
- Quickstart
- How-tos
- Specify a project name
- Use lifecycle hooks
- Use service profiles
- Control startup order
- Use environment variables
- Set environment variables
- Environment variables precedence
- Pre-defined environment variables
- Interpolation
- Best practices
- Build dependent images
- Use Compose Watch
- Secrets in Compose
- Networking
- Use multiple Compose files
- Merge
- Extend
- Include
- Enable GPU support
- Use Compose in production
- OCI artifact applications New
- Use provider services New
- Compose Bridge
- Usage
- Customize
- Use Model Runner
- Compose SDK New
- Support and feedback
- FAQs
- Give feedback
- Sample apps
- Releases
- Release notes
- Prior releases
- Migrate to Compose v2
- Introduction to Compose
- Testcontainers
- cagent Experimental
- Model providers
- Local models
- Building a coding agent
- Best practices
- Sharing agents
- Integrations
- A2A
- ACP
- MCP
- Reference
- Configuration file
- Toolsets
- CLI
- Examples
- RAG
- Evals
- MCP Catalog and Toolkit Beta
- Get started
- MCP Catalog
- MCP Toolkit
- Dynamic MCP New
- MCP Gateway
- Hub MCP server
- Security FAQs
- E2B sandboxes
- Docker Sandboxes Experimental
- Get started
- Configure Claude Code
- Advanced
- Troubleshooting
- Model Runner
- Get started with DMR
- DMR REST API
- DMR examples
- Ask Gordon Beta
- Model Context Protocol (MCP)
- Built-in tools in Gordon
- Configure MCP servers with YAML
- Model Context Protocol (MCP)
- AI and Docker Compose
- Use AI models in Compose New
- Docker Hardened Images New
- Quickstart
- Features
- Explore
- Hardened images
- Build process
- Image types
- Image testing
- Responsibility overview
- Feedback
- Migration
- Migration checklist
- AI-assisted migration Experimental
- Migrate from Alpine or Debian
- Migrate from Wolfi
- Migration examples
- Go
- Python
- Node.js
- How-tos
- Explore images
- Mirror a repository
- Customize an image or chart
- Use an image
- Use an image in Kubernetes
- Use a Helm chart
- Manage images and charts
- Use Extended Lifecycle Support
- Compare images
- Verify an image or chart
- Scan an image
- Enforce image usage
- Debug a container
- Core concepts
- Attestations
- CIS Benchmark
- Code signing
- CVEs
- Distroless images
- FIPS
- glibc and musl
- Hardening
- Image digests
- Image provenance
- Immutability
- SBOMs
- SLSA
- Software Supply Chain Security
- SSDLC
- STIG
- VEX
- Troubleshoot
- Additional resources
- Docker Desktop
- Setup
- Install
- Mac
- Mac permission requirements
- Windows
- Windows permission requirements
- Linux
- Ubuntu
- Debian
- Fedora
- Arch
- RHEL
- VM or VDI environments
- Sign in
- Allowlist
- Install
- Explore Docker Desktop
- Containers
- Images
- Volumes
- Builds
- Kubernetes
- Resource Saver mode
- Pause Docker Desktop
- Features and capabilities
- Networking
- How-tos
- GPU support
- USB/IP support
- Synchronized file shares
- containerd image store
- Wasm workloads Beta
- Docker Desktop CLI
- Virtual Machine Manager
- WSL
- Best practices
- Custom kernels on WSL
- Use WSL
- Networking
- Settings and maintenance
- Change settings
- Backup and restore data
- Troubleshoot and support
- Troubleshoot and diagnose
- Common topics
- Known issues
- MacOS app damaged dialog
- FAQs
- General
- Mac
- Windows
- Linux
- Releases
- Give feedback
- Troubleshoot and diagnose
- Uninstall
- Release notes
- Setup
- Docker Offload Early Access
- Quickstart
- About
- Configure
- Usage & billing
- Optimize usage
- Troubleshoot
- Give feedback
- Docker Build Cloud
- Setup
- Usage
- Continuous integration
- Optimization
- Builder settings
- Release notes
- Docker Hub
- Quickstart
- Library
- Search
- Trusted content
- Catalogs
- Mirror
- Repositories
- Create
- Manage
- Repository information
- Access
- Images
- Tags
- Immutable tags
- Image Management
- Software artifacts
- Push images
- Move images
- Bulk migrate Docker images
- Image security insights
- Webhooks
- Automated builds
- Set up
- Link accounts
- Automated repository tests
- Advanced options
- Manage autobuilds
- Troubleshoot
- Trusted content
- Docker Official Images
- Docker Verified Publisher Program
- Docker-Sponsored Open Source Program
- Insights and analytics
- Export repositories
- Archive
- Delete
- Personal settings
- Usage and limits
- Pulls
- Optimize usage
- Service accounts
- Troubleshoot
- Release notes
- Docker Scout
- Install
- Quickstart
- Explore
- Dashboard
- Docker Scout image analysis
- Docker Scout metrics exporter
- Image details view
- Manage vulnerability exceptions
- How-tos
- Create an exception using the GUI
- Create an exception using the VEX
- Docker Scout environment variables
- Docker Scout SBOMs
- Use Scout with different artifact types
- Deep dive
- Advisory database sources and matching service
- Data collection and storage in Docker Scout
- Policy Evaluation
- Configure policies
- Docker Scout health scores
- Evaluate policy compliance in CI
- Remediation with Docker Scout
- View Docker Scout policy status
- Integrations
- Code quality
- SonarQube
- Container registries
- Amazon ECR
- Artifactory Container Registry
- Azure Container Registry
- Continuous Integration
- Azure DevOps Pipelines
- Circle CI
- GitHub Actions
- GitLab CI/CD
- Jenkins
- Integrating Docker Scout with environments
- Generic (CLI)
- Sysdig
- Source code management
- GitHub
- Team collaboration
- Slack
- Code quality
- Release notes
- CLI release notes
- Platform release notes
- Docker Extensions
- Marketplace extensions
- Non-marketplace extensions
- Configure a private marketplace
- Settings and feedback
- Extensions SDK
- The build and publish process
- Quickstart
- Part one: Build
- Create a simple extension
- Create an advanced frontend extension
- Add a backend to your extension
- Part two: Publish
- Add labels
- Validate
- Package and release your extension
- Share your extension
- Publish in the Marketplace
- Build multi-arch extensions
- Architecture
- Metadata
- Security
- Design and UI styling
- Guidelines
- Docker design principles
- MUI best practices
- Developer Guides
- Authentication
- Interacting with Kubernetes
- Invoke host binaries
- Use the Docker socket
- Developer SDK tools
- Test and debug
- Continuous Integration (CI)
- CLI reference
- Extension APIs
- Dashboard
- Docker
- Extension Backend
- Extension UI API
- Navigation
- Testcontainers Cloud
- Deprecated products and features
- Release lifecycle
- Support
- Billing
- Add or update a payment method
- Manage your billing information
- 3D Secure authentication
- Invoices and billing history
- Change your billing cycle
- Submit a tax exemption certificate
- FAQs
- Docker accounts
- Accounts
- Create an account
- Manage an account
- Deactivate an account
- Security
- Personal access tokens
- Two-factor authentication
- Recover your Docker account
- FAQs
- General
- Container
- Network and VM
- Security announcements
- Subscription
- Compare subscription
- Set up your subscription
- Scale your subscription
- Manage seats
- Change your subscription
- Docker Desktop license agreement
- FAQs
- Release notes
- Administration
- Organization administration
- Create your organization
- Onboard your organization
- Manage organization members
- Convert an account into an organization
- Create and manage a team
- Deactivate an organization
- Manage Docker products
- Activity logs
- Organization information
- Insights
- Company administration overview
- Create a company
- Manage company members
- Manage company organizations
- Manage company owners
- FAQ
- Organization
- Company
- Organization administration
- Deploy Docker Desktop
- MSI installer
- PKG installer
- MS Store
- Deploy with Intune
- Deploy with Jamf Pro
- Microsoft Dev Box
- FAQs
- Security
- Single sign-on
- Configure
- Connect
- FAQs
- General
- Domains
- Enforcement
- Identity providers
- User management
- Manage
- Provision
- Just-in-Time
- SCIM
- Group mapping
- Enforce sign-in
- Configure
- Roles and permissions
- Core roles
- Custom roles
- Manage domains
- Hardened Docker Desktop
- Enhanced Container Isolation
- Enable ECI
- Configure advanced settings
- Limitations
- FAQs
- Settings Management
- Use a JSON file
- Use the Admin Console
- Desktop settings reporting
- Settings reference
- Registry Access Management
- Image Access Management
- Air-gapped containers
- Enhanced Container Isolation
- Organization access tokens
- Single sign-on
- Troubleshoot
- Troubleshoot provisioning
- Troubleshoot SSO
- Prerequisites
- Firewall limitations
- OS requirements
- Uninstall old versions
- Installation methods
- Install using the apt repository
- Upgrade Docker Engine
- Install from a package
- Upgrade Docker Engine
- Install using the convenience script
- Install pre-releases
- Upgrade Docker after using the convenience script
- Uninstall Docker Engine
- Next steps
To get started with Docker Engine on Ubuntu, make sure you meet the prerequisites, and then follow the installation steps.
Prerequisites
Firewall limitations
WarningBefore 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.
- 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.
OS requirements
To install Docker Engine, you need the 64-bit version of one of these Ubuntu versions:
- Ubuntu Questing 25.10
- Ubuntu Plucky 25.04
- Ubuntu Noble 24.04 (LTS)
- Ubuntu Jammy 22.04 (LTS)
Docker Engine for Ubuntu is compatible with x86_64 (or amd64), armhf, arm64, s390x, and ppc64le (ppc64el) architectures.
NoteInstallation on Ubuntu derivative distributions, such as Linux Mint, is not officially supported (though it may work).
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-compose-v2
- 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:
$ sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-compose-v2 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 section.
Installation methods
You can install Docker Engine in different ways, depending on your needs:
Docker Engine comes bundled with Docker Desktop for Linux. This is the easiest and quickest way to get started.
Set up and install Docker Engine from Docker's apt repository.
Install it manually and manage upgrades manually.
Use a convenience script. Only recommended for testing and development environments.
Apache License, Version 2.0. See LICENSE for the full license.
Install using the apt 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.
# 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/ubuntu/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/ubuntu Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}") Components: stable Signed-By: /etc/apt/keyrings/docker.asc EOF sudo apt updateInstall the Docker packages.
Latest Specific versionTo install the latest version, run:
$ sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginTo install a specific version of Docker Engine, start by listing the available versions in the repository:
$ apt list --all-versions docker-ce docker-ce/noble 5:29.1.3-1~ubuntu.24.04~noble <arch> docker-ce/noble 5:29.1.2-1~ubuntu.24.04~noble <arch> ...Select the desired version and install:
$ VERSION_STRING=5:29.1.3-1~ubuntu.24.04~noble $ sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-pluginNote
The Docker service starts automatically after installation. To verify that Docker is running, use:
$ sudo systemctl status dockerSome systems may have this behavior disabled and will require a manual start:
$ sudo systemctl start dockerVerify that the installation is successful by running the hello-world image:
$ sudo docker run hello-worldThis 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.
TipReceiving 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 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, 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.
Go to https://download.docker.com/linux/ubuntu/dists/.
Select your Ubuntu 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.
$ 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>.debNote
The Docker service starts automatically after installation. To verify that Docker is running, use:
$ sudo systemctl status dockerSome systems may have this behavior disabled and will require a manual start:
$ sudo systemctl start dockerVerify that the installation is successful by running the hello-world image:
$ sudo docker run hello-worldThis 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.
TipReceiving 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 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, pointing to the new files.
Install using the convenience script
Docker provides a convenience script at 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 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.
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.
TipPreview script steps before running. You can run the script with the --dry-run option to learn what steps the script will run when invoked:
$ 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/ and runs it to install the latest stable release of Docker on Linux:
$ 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. 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).
Install pre-releases
Docker also provides a convenience script at 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:
$ curl -fsSL https://test.docker.com -o test-docker.sh $ sudo sh test-docker.shUpgrade 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:
$ sudo apt purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extrasImages, containers, volumes, or custom configuration files on your host aren't automatically removed. To delete all images, containers, and volumes:
$ sudo rm -rf /var/lib/docker $ sudo rm -rf /var/lib/containerdRemove source list and keyrings
$ 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.
Edit this page
Request changes
Table of contents- Prerequisites
- Firewall limitations
- OS requirements
- Uninstall old versions
- Installation methods
- Install using the apt repository
- Upgrade Docker Engine
- Install from a package
- Upgrade Docker Engine
- Install using the convenience script
- Install pre-releases
- Upgrade Docker after using the convenience script
- Uninstall Docker Engine
- Next steps
Từ khóa » Cái Engine
-
HCCI And CAI Engines For The Automotive Industry | ScienceDirect
-
Hcci And Cai Engines For The Automotive Industry - 1st Edition
-
Schematic Diagram Of The Direct-injection-type CAI Engine System.
-
Motivation, Definition And History Of HCCI/CAI Engines - ResearchGate
-
2-Stroke CAI Operation On A Poppet Valve DI Engine Fuelled With ...
-
Chế Động Cơ Đẩy Siêu Khỏe Từ 4 Cái Motor 180 | Yêu Sáng Tạo
-
Cài đặt Unreal Engine 5 Preview Phiên Bản Cập Nhật Mới Nhất
-
Effects Of Intake Valve Timing On Premixed Gasoline Engine - JStor
-
Engine And Fuel Related Issues Of Gasoline CAI (Controlled Auto ...
-
Methods To Achieve HCCI/CAI Combustion At Idle Operation In A ...
-
Hướng Dẫn Cài đặt Blade & Soul Unreal Engine 4
-
Unreal Engine: Phần Mềm Hỗ Trợ Tạo Game, Phát Triển Game