Docker Engine Requirements
Flexible Deployment Options is available now
Terraform Enterprise can now be run natively on Docker with Flexible Deployment Options. The Docker Flexible Deployment Option allows for a faster installation and startup time, reduction in resource requirements, improved security and supports Docker Compose.Terraform Enterprise requires at least one of the following Docker Engine configurations, in order of preference:
- Docker Engine 24.x or 23.x
- Docker Engine 1.13.1 from the Extra Packages for Enterprise Linux (EPEL) repository using a modified
libseccomp
profile.
Docker v20.10 is only supported on Amazon Linux 2. Docker v20.10 is no longer receiving updates from Docker, including security updates. Customers using Amazon Linux 2 are encouraged to move to an operating system that supports Docker 23 or 24. In order run Docker v20.10, you will need one of the following:
New online installations of Terraform Enterprise install a supported version of Docker Engine by default. Alternatively, you can install Docker Engine manually as long as you adhere to the above requirements.
Upgrades to Terraform Enterprise do not upgrade Docker Engine. It is your responsibility to keep Docker Engine up to date within these requirements to ensure stability and security.
Docker Compose Compatibility
Docker Engine comes prepackaged with docker compose. Docker 1.13.1 has a unique path for docker compose.
Code snippets and commands assume that docker compose is accessible with the docker compose
syntax and should be modified, replacing docker compose
with docker-compose
when Docker Engine 1.13.1 is installed.
Docker Engine With a Compatible runc
Version
Install a supported Docker Engine version.
Install the latest version of
containerd
for your operating system.
On Debian/Ubuntu:
On RHEL/CentOS:
- Confirm that the installed
containerd
version is 1.4.9, 1.5.5, or greater.
- Confirm that the installed
runc
version is v1.0.0-rc93 or greater:
- If your Docker Engine and
runc
versions meet the requirements from previous steps, your system is properly configured. Otherwise, proceed to option 2.
Docker Engine With a Compatible libseccomp
Version
Note: These instructions should only be used if your operating system does not meet the requirements detailed in Docker Engine With a Compatible runc
Version.
Install a supported Docker Engine version.
Install the latest version of
libseccomp
for your operating system.
On Debian/Ubuntu:
On RHEL/CentOS:
- Confirm that the installed
libseccomp
version is 2.4.4 or greater.
- If your Docker Engine and
libseccomp
versions meet the requirements from previous steps, your system is properly configured. Otherwise, proceed to option 3.
Docker Engine Using a Modified libseccomp
Profile
Note: These instructions should only be used if your operating system does not meet the requirements detailed in either Docker Engine With a Compatible runc
Version or Docker Engine With a Compatible libseccomp
Version.
Install a supported Docker Engine version.
Check if the file
/etc/docker/seccomp.json
exists. If it does, proceed to step 4.Download the default moby
libseccomp
profile and save it to the file/etc/docker/seccomp.json
.
- In the
/etc/docker/seccomp.json
file, change"defaultAction": "SCMP_ACT_ERRNO",
to"defaultAction": "SCMP_ACT_TRACE",
.
Docker Engine 1.13.1 (RHEL only): After modifying the /etc/docker/seccomp.json
file, proceed to step 8.
- Create a drop-in systemd unit file for the
docker
systemd service.
- Edit the drop-in
/etc/systemd/system/docker.service
systemd unit file and modify the line starting withExecStart=
to include the option--seccomp-profile=/etc/docker/seccomp.json
.
For example, the following line:
Would become:
- Reload the systemd daemon.
- Restart Docker Engine.