Skip to content

Latest commit

 

History

268 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

tpm2-software-container

This repository contains metadata and scripts used to generate the container images used for continuous integration (CI) by the various tpm2-software projects.

Local build

To build the container image locally invoke Docker or Podman with the build command generated using make from within the tpm2-software-container directory. For example:

make

# Build Ubuntu 20.04 image using Docker
docker build -f ./ubuntu-20.04.docker

# Build Fedora 32 image using Podman, squashing all intermediate layers together
podman build --squash -f ./fedora-32.docker

The final output of the build will be an IMAGE ID which can be used to run the container image, for example:

docker run -it <IMAGE ID> /bin/bash

or to run the tpm2-tools CI sequence locally:

docker run --rm --env-file /path/to/tpm2-tools/.ci/docker.env -v /path/to/tpm2-tools:/workspace/tpm2-tools <IMAGE ID> /bin/bash -c '/workspace/tpm2-tools/.ci/docker.run'

or to run the tpm2-tss CI sequence locally

docker run --rm --env-file /path/to/tpm2-tss/.ci/docker.env -v /path/to/tpm2-tss:/workspace/tpm2-tss <IMAGE ID> /bin/bash -c '/workspace/tpm2-tss/.ci/docker.run'

Auto builds

The repository is monitored by Github Actions and repository changes are built and submitted to Github Container Registry. The containers are listed on tpm2software/packages.

For example, to download and run a container based on Fedora 32 from the registry:

# With Docker
docker run -it --rm ghcr.io/tpm2-software/fedora-32 /bin/bash

# With Podman
podman run -it --rm ghcr.io/tpm2-software/fedora-32 /bin/bash

Structure

Standard distro/version images have profile-tag variants using the same base name:

  • <distro>-<version>-dev
  • <distro>-<version>-pkcs11

This intentionally excludes architecture-specific tags and specialized images such as *-mbedtls-*, which remain single-purpose variants.

Profile intent:

  • base tag (<distro>-<version>): lean/default CI dependencies
  • dev tag (<distro>-<version>-dev): base plus development/tooling extras
  • pkcs11 tag (<distro>-<version>-pkcs11): dev plus pkcs11/python/java extras

About

Container building stuff

Resources

Stars

17 stars

Watchers

7 watching

Forks

Releases

Packages

Used by

Contributors

Languages