https://github.com/containerscrew/infratools
Container image with infra tools (terraform, terragrunt, aws cli, helm, kubectl...). Useful for CI/CD.
https://github.com/containerscrew/infratools
alpine awscliv2 cd ci ci-cd helm k8s terraform terragrunt tftools
Last synced: 17 days ago
JSON representation
Container image with infra tools (terraform, terragrunt, aws cli, helm, kubectl...). Useful for CI/CD.
- Host: GitHub
- URL: https://github.com/containerscrew/infratools
- Owner: containerscrew
- License: apache-2.0
- Created: 2024-03-19T12:05:41.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-03-06T17:15:23.000Z (about 2 months ago)
- Last Synced: 2025-03-28T19:53:42.838Z (about 1 month ago)
- Topics: alpine, awscliv2, cd, ci, ci-cd, helm, k8s, terraform, terragrunt, tftools
- Language: Shell
- Homepage:
- Size: 460 KB
- Stars: 2
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
infratools
Container image with infra tools (terraform, terragrunt, aws cli, helm, kubectl...). Useful for CI/CD.
**Table of Contents** *generated with [mtoc](https://github.com/containerscrew/mtoc)*
- [Badges](#badges)
- [About](#about)
- [Architecture](#architecture)
- [Main tools](#main-tools)
- [Versioning](#versioning)
- [Installing python libraries](#installing-python-libraries)
- [Use pipx to install python packages/libraries](#use-pipx-to-install-python-packages/libraries)
- [Use venv](#use-venv)
- [Force installation with pip3](#force-installation-with-pip3)
- [Global gitconfig for internal git servers with self signed certificate](#global-gitconfig-for-internal-git-servers-with-self-signed-certificate)
- [Lint](#lint)
- [Image security scan with Trivy](#image-security-scan-with-trivy)
- [Local trivy scan](#local-trivy-scan)
- [Local dev](#local-dev)
- [Using `run.sh` script (Recommended)](#using-`run.sh`-script-(recommended))
- [TODO](#todo)
- [CHANGELOG](#changelog)
- [LICENSE](#license)
# Badges
[](https://github.com/containerscrew/infratools/actions/workflows/build.yml)
[](/LICENSE)
[](https://hub.docker.com/r/containerscrew/infratools/)
# About
How many times do you need a container image with tools like `terraform, helm, kubectl, aws cli, terragrunt`... among many others? Aren't you tired of having to maintain all of them in each repository, instead of having one **"general"** one that can be used in multiple repos?
**Available tags:** https://hub.docker.com/r/containerscrew/infratools/tags
# Architecture
| Arch | Supported | Tested |
|---------|----------|--------|
| amd64 | ✅ | ✅ |
| arm64 | ✅ | ✅ |
# Main tools
| Tool | Available |
|------------------------------------------------------|----------|
| Terraform | ✅ |
| Terragrunt | ✅ |
| Kubectl | ✅ |
| Helm | ✅ |
| AWS CLI | ✅ |
| [tftools](https://github.com/containerscrew/tftools) | ✅ |
| [tfenv](https://github.com/tfutils/tfenv) | ✅ |
| [ohmyzsh](https://ohmyz.sh/) | ✅ |
Take a look to all the available installed tools inside the [Dockerfile](./Dockerfile)
> [!TIP]
> You can change `terraform` version dynamically using `tfenv` or setting `.terraform-version` file in your repository.
# Versioning
* Alpine core packages: https://pkgs.alpinelinux.org/packages
* AWS cli v2 is installed directly from official alpine repository. If you need to look for other version, [visit this page](https://pkgs.alpinelinux.org/packages?name=aws-cli&branch=edge&repo=&arch=&maintainer=)
* For every new version, a new git tag will be created. You can see versioning inside [Dockerfile](./Dockerfile)
# Installing python libraries
If you try to install python libraries using `pip3`, you will see the following error:
Error:
× This environment is externally managed
╰─>
The system-wide python installation should be maintained using the system
package manager (apk) only.
If the package in question is not packaged already (and hence installable via
"apk add py3-somepackage"), please consider installing it inside a virtual
environment, e.g.:
python3 -m venv /path/to/venv
. /path/to/venv/bin/activate
pip install mypackage
To exit the virtual environment, run:
deactivate
The virtual environment is not deleted, and can be re-entered by re-sourcing
the activate file.
To automatically manage virtual environments, consider using pipx (from the
pipx package).
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
## Use pipx to install python packages/libraries
Install library + deps:
```shell
pipx install boto3 --include-deps
```
Install a package:
```shell
pipx install your-package-name # visit pypip
```
## Use venv
```shell
python3 -m venv /path/to/venv
. /path/to/venv/bin/activate
pip3 install mypackage
```
## Force installation with pip3
```shell
pip3 install boto3 --break-system-packages
```
# Global gitconfig for internal git servers with self signed certificate
If using custom git repository with self signed certificate, just edit in your `~/.gitconfig`:
```bash
[http "https://gitlab.server.internal"]
##################################
# Self Signed Server Certificate #
##################################
sslCAInfo = /path/to/your/certificate.crt
#sslCAPath = /path/to/selfCA/
sslVerify = true # or set to false if you trust
```
# Lint
```shell
make hadolint
```
# Image security scan with Trivy
This image uses [trivy github action](https://github.com/aquasecurity/trivy-action) as a tool for security scanning.
Take a look to the [official repo](https://github.com/aquasecurity/trivy) of Trivy.
## Local trivy scan
[Install trivy](https://aquasecurity.github.io/trivy/test/getting-started/installation/)
```shell
make build-image
make trivy-scan # trivy image docker.io/containerscrew/infratools:test
```
# Local dev
```shell
make local-build
make local-run
# Or all in one
make local-build-run
```
> Use other version([tag](https://github.com/containerscrew/infratools/tags)) if needed (edit the Makefile).
# Using `run.sh` script (Recommended)
Create a copy of the script [`run.sh`](./run.sh) in your repository and run it.
```shell
./run.sh
Usage: ./run.sh [-i (info)] [-u (update)] [-a (attach)]
```
With this script, you can run the container or attach to an existing, update the container to the latest tag version, or get the current version of the container.
> [!IMPORTANT]
> Running this script, ZSH history will be saved in /code repository to allow persistent command history.
> So, If you don't want to push the .zsh_history to git, add the file to `.gitignore` in the repo you are using.
# TODO
* Add other dynamic version switchers for other tools (tgswitch, kubectl...)
* Seperate pipeline for build release + build in other branch
# CHANGELOG
[`CHANGELOG.md`](./CHANGELOG.md)
# LICENSE
[`LICENSE`](./LICENSE)