oowy/infracost repository overview

⁠Quick reference

• Maintained by:
  Oowy team⁠

• Where to get help:
  the Docker Community Slack⁠, Server Fault⁠, Unix & Linux⁠, or Stack Overflow⁠

⁠Supported tags

Based on Alpine Linux 3.20

• latest
• 0.10.41-alpine3.20 0.10.40-alpine3.20

Based on Alpine Linux 3.19

• 0.10.39-alpine3.19 0.10.38-alpine3.19 0.10.37-alpine3.19 0.10.36-alpine3.19 0.10.35-alpine3.19 0.10.34-alpine3.19 0.10.33-alpine3.19 0.10.32-alpine3.19 0.10.31-alpine3.19 0.10.30-alpine3.19

Based on Alpine Linux 3.18

• 0.10.39-alpine3.18 0.10.38-alpine3.18 0.10.37-alpine3.18 0.10.36-alpine3.18 0.10.35-alpine3.18 0.10.34-alpine3.18 0.10.33-alpine3.18 0.10.32-alpine3.18 0.10.31-alpine3.18 0.10.30-alpine3.18

⁠Quick reference (cont.)

• Supported architectures: amd64, arm64v8

⁠What is Infracost?

Infracost is an open-source tool that helps estimate and display the potential cost of cloud infrastructure resources defined in Infrastructure as Code (IaC) configuration files. This tool supports popular IaC platforms like Terraform and provides cost estimates for various cloud service providers, such as AWS, Google Cloud, and Azure.

Infracost assists development and operations teams in understanding and managing cloud infrastructure costs by providing early indications of potential costs before deployment. This enables making more informed decisions and avoiding unexpected or unnecessary expenses.

⁠Infracost Docker Images

The team publishes a Docker image to this repository for each official release of Infracost.

These images wrap the infracost executable, allowing you to run infracost subcommands by passing in their names and arguments as part of docker run.

⁠Configuration

You will likely need to further configure your container so that infracost can access your configuration files and provider credentials. This could include mounting your configuration into the container, setting the working directory to refer to your configuration, and passing in environment variables and credentials files for the providers you intend to use. The docker run documentation lists the options you can use to customize the container environment.

You could also use these images as a base for your own images. For example, this would be helpful if you wanted to to pre-set CLI Configuration settings as part of your image.

⁠Community

Open issues about Infracost binary on the main Infracost repository⁠.