Skip to content

Versioning#

Tools#

We package the latest versions of the tools that are available at a release time for the official BitOps Docker images. Check out BitOps Releases to understand which versions are currently shipped.

If you need specific versions or tools, you can build your own image with the custom plugins.

Images#

BitOps Docker images are packaged and hosted on Docker Hub. Here is how these images are named, versioned and tagged.

  • An image with a version tag containing a semver (e.g. 2.0.0) is immutable and refers to the stable release.
  • A version tag equal to latest is always mutable and points to the latest stable release.
  • A version tag containing dev is always mutable and refers to the current development state in the main repository branch.
  • A version tag containing omnibus points to the default image that includes recommended DevOps tools.
  • A version tag containing base refers to a minimal image with no other tools. You can build a custom BitOps image from it.

Official Images#

To clear up any potential confusion regarding the versioning of the bitovi/bitops image, we use the following table.

Image Name PreInstalled Tools Docker image name Supported Cloud provider Additional stable image tags Development image tags (main branch)
omnibus Terraform
Cloudformation
Ansible
Helm
Kubectl
AWS CLI		 bitovi/bitops:2.0.0-omnibus AWS latest
2.0.0		 dev
aws-terraform Terraform
AWS CLI		 bitovi/bitops:2.0.0-aws-terraform AWS
aws-ansible Ansible
AWS CLI		 bitovi/bitops:2.0.0-aws-ansible AWS
aws-helm Helm
Terraform
AWS CLI		 bitovi/bitops:2.0.0-aws-helm AWS
base BitOps source bitovi/bitops:2.0.0-base - base dev-base

Image tag pinning#

  • We always recommend pinning the stable version of BitOps to avoid any breaking changes like bitovi/bitops:2.0.0.
  • If the security is higher priority for you, use sha256 digest like bitovi/bitops:sha256:82becede498899ec668628e7cb0ad87b6e1c371cb8a1e597d83a47fac21d6af3.

See more in the docker documentation.