Skip to content

Releases: concourse/oci-build-task

v0.13.1

06 Jun 18:26
135fbe7
Compare
Choose a tag to compare

What's Changed

  • Add qemu binaries back into the image to fix exec format error by @taylorsilva in #136

Full Changelog: v0.13.0...v0.13.1

v0.13.0

05 Jun 19:47
b9dfc25
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.12.0...v0.13.0

v0.12.0

22 May 16:17
9c9b40e
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.11.1...v0.12.0

v0.11.1

14 Feb 03:28
1aac28e
Compare
Choose a tag to compare

What's Changed

  • Bump buidkit to 0.11.0 to fix an error when building multi-arch image by @evanchaoli in #109

New Contributors

Full Changelog: v0.11.0...v0.11.1

v0.11.0

28 Sep 16:40
9c2df86
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.10.0...v0.11.0

v0.10.0

06 May 18:08
a46d096
Compare
Choose a tag to compare
  • Adds support for BUILDKIT_SECRETTEXT_* #88

v0.9.1

29 Oct 20:50
4bf5360
Compare
Choose a tag to compare
  • Fixes a bug with IMAGE_ARG_* where if the arg was uppercase the build would fail with an error. Image args can now be all or partially uppercase

v0.9.0

16 Jul 18:02
7068da6
Compare
Choose a tag to compare
  • Add image_platform which allows users to build images for platforms that don't match the current platform

v0.8.0

16 Jul 18:00
5caf261
Compare
Choose a tag to compare

Bumps buildkit

v0.7.0

12 Jan 16:01
Compare
Choose a tag to compare

this release adds support for using pre-fetched images in FROM ...! this pattern allows you to version and fetch your base image with Concourse and pass it along to the oci-build task to use directly rather than querying the registry and fetching it at build time (possibly resolving to a different version than the build triggered with).

in your oci-build task config, configure a IMAGE_ARG_* param and corresponding input:

inputs:
- name: golang

params:
  IMAGE_ARG_base_image: golang/image.tar

in your Dockerfile, change the FROM so that it can be passed as a build arg:

ARG base_image=golang
FROM ${base_image}

in your pipeline, add a resource and a get step for fetching the image:

resources:
- name: golang
  type: registry-image
  source: {repository: golang}

jobs:
- name: build
  plan:
  - get: golang
    params: {format: oci}
  - task: build
    # ...

this feature resolves quite a few issues:

  • #1 - the primary feature request, calling for something analogous to load_base[s] from the docker-image resource.
  • #2 - configurable CA certs for image fetching in FROM
  • #3 & #14 - insecure & authenticated registries in FROM
    • you guessed it, just fetch it using a resource instead

how does this work?

it's kinda neat! the oci-build-task just runs a teeny tiny Docker registry on localhost that serves the OCI/docker image tarballs configured as image args, and then it passes addresses like localhost:45431/base_image as build args to the Dockerfile.

side note: if we ever do decide to switch to Kaniko (#46), the pattern will be the same; see concourse/docker-image-resource#190 (comment)