Name		Name	Last commit message	Last commit date
.lighthouse/jenkins-x		.lighthouse/jenkins-x
all-sdks-alpine		all-sdks-alpine
all-sdks-debian		all-sdks-debian
android		android
black-arch		black-arch
bun		bun
chrome-for-testing-golang		chrome-for-testing-golang
chrome-for-testing		chrome-for-testing
container-tools		container-tools
docksec		docksec
golang-pipeline		golang-pipeline
helmfile		helmfile
net8-integration-tests		net8-integration-tests
net8-playwright		net8-playwright
net8-sonar		net8-sonar
nginx		nginx
node-unit-test		node-unit-test
node		node
python310-torch-cpu		python310-torch-cpu
python310-torch-cuda		python310-torch-cuda
python310		python310
python314		python314
terratest-tfsec		terratest-tfsec
tflint		tflint
.gitignore		.gitignore
LICENSE		LICENSE
LastAutoCommit		LastAutoCommit
OWNERS		OWNERS
OWNERS_ALIASES		OWNERS_ALIASES
README.md		README.md

Repository files navigation

Dockerfiles

Top level container images used in MQube services. We should probably get rid of these and use image caching layers instead.

Adding a new container image

Create a folder containing the Dockerfile you wish to use in the root of the repository. The name of this folder will become the name of the generated image.
In /.lighthouse/jenkins-x/ copy one of the existing folders and rename it to the name of image.
Change the environment variable IMAGE_NAME in pr.yaml & release.yaml to be the name of the image.
Open a PR with your changes.

About

Container images without high and critical vulnerabilities

Custom properties

0 stars

1 watching

Report repository

Releases

Packages

Used by

Contributors

Languages