<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/classes/container-registry.bbclass, branch master-next</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2026-02-09T03:34:12+00:00</updated>
<entry>
<title>container-registry: add secure registry infrastructure with TLS and auth</title>
<updated>2026-02-09T03:34:12+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2026-02-09T03:17:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=092aa81983335b2346a725eebd2a75fc785bb42b'/>
<id>urn:sha1:092aa81983335b2346a725eebd2a75fc785bb42b</id>
<content type='text'>
Add opt-in secure registry mode with auto-generated TLS certificates
and htpasswd authentication.

New BitBake variables:
  CONTAINER_REGISTRY_SECURE - Enable TLS (HTTPS) for local registry
  CONTAINER_REGISTRY_AUTH - Enable htpasswd auth (requires SECURE=1)
  CONTAINER_REGISTRY_USERNAME/PASSWORD - Credential configuration
  CONTAINER_REGISTRY_CERT_DAYS/CA_DAYS - Certificate validity
  CONTAINER_REGISTRY_CERT_SAN - Custom SAN entries

The bbclass validates conflicting settings (AUTH without SECURE) and
provides credential helper functions for skopeo push operations.

PKI infrastructure (CA + server cert with SAN) is auto-generated at
bitbake build time via openssl-native. The generated helper script
supports both TLS-only and TLS+auth modes.

The script now supports environment variable overrides for
CONTAINER_REGISTRY_STORAGE, CONTAINER_REGISTRY_URL, and
CONTAINER_REGISTRY_NAMESPACE, uses per-port PID files to allow
multiple instances, and auto-generates config files when running
from an overridden storage path.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>container-registry: add industry-standard tag strategies</title>
<updated>2026-02-09T03:32:52+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2026-01-12T20:14:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=1d8968199aa812d5c9bdc8089e0eb53da25cd877'/>
<id>urn:sha1:1d8968199aa812d5c9bdc8089e0eb53da25cd877</id>
<content type='text'>
Add comprehensive tag support for registry push operations:

Tag strategies (CONTAINER_REGISTRY_TAG_STRATEGY):
- sha/git: short git commit hash for traceability
- branch: git branch name (sanitized) for dev workflows
- semver: nested SemVer tags (1.2.3 -&gt; 1.2.3, 1.2, 1)
- timestamp: YYYYMMDD-HHMMSS format
- version: single version tag from PV
- latest: the "latest" tag
- arch: append architecture suffix

Helper script enhancements:
- push --tag &lt;tag&gt;: explicit tags (repeatable)
- push --strategy &lt;strategies&gt;: override tag strategy
- push --version &lt;ver&gt;: version for semver strategy
- Baked-in defaults from bitbake variables
- Environment variable overrides supported

This aligns with industry practices:
- Git SHA for CI/CD traceability
- SemVer nested tags for release management
- Branch tags for feature development

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>container-registry: add local OCI registry infrastructure</title>
<updated>2026-02-09T03:32:52+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2026-01-12T16:09:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=87ed625c043e4cdbabf569227b189823cd08db8e'/>
<id>urn:sha1:87ed625c043e4cdbabf569227b189823cd08db8e</id>
<content type='text'>
Add container registry support for Yocto container workflows:
- container-registry.bbclass with helper functions
- container-registry-index.bb generates helper script with baked paths
- docker-registry-config.bb for Docker daemon on targets
- container-oci-registry-config.bb for Podman/Skopeo/Buildah targets
- IMAGE_FEATURES container-registry for easy target configuration

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
