bstick12 / pack-concourse-resource

Concourse Resource that uses Pack CLI to build container images

Pack CLI Concourse Resource

You should probably look at using the lifecycle-build task instead of this resource.

---

A proof of concept concourse resource that builds OCI images using the pack-cli

Uses Docker in Docker so must be run a privileged.

It borrows heavily from the docker-image-resource

It utilizes the in and check behaviours from the registry-image-resource

Currently will only work with buildpacks that are build using pack > v0.0.9

Source Configuration

• repository: Required. The name of the repository that you want to build e.g bstick12/built-with-pack
• tag: Optional. The tag value for the image. Defaults to latest
• username: Required. The username to authenticate with when pushing
• password: Required. The password to use when authenticating

Behaviour

check: Discover new digests

See registry-image-resource/check

in: Fetch the image's rootfs and metadata

See registry-image-resource/in

out: Build an OCI image using the pack CLI and push to a repository

Parameters

• build: Required. The source code to build in to the OCI image.
• builder: Optional. The builder to use to build the OCI image.
• tag: Optional. Name of tag. Defaults to latest. Overridden by tag_file.
• tag_file: Optional. The value should be a path to a file containing the name of the tag.
• tag_prefix: Optional. If specified, the tag read from the file will be prepended with this string. This is useful for adding v in front of version numbers.

Example

---
resources:
- name: git-resource
  type: git
  source: # ...

- name: pack-built-image
  type: pack-image-resource
  source:
    repository: ((image-name))
    email: ((docker-hub-email))
    username: ((docker-hub-username))
    password: ((docker-hub-password))

resource_types:
- name: pack-image-resource
  type: docker-image
  privileged: true
  source:
    repository: bstick12/pack-concourse-resource
    version: latest

jobs:
- name: build-source-using-pack-image-resource
  plan:
  - get: git-resource
    trigger: true
  - put: pack-built-image
    params:
      build: pack-built-image
      builder: ((pack-builder-image))

pack-concourse-resource's Issues

Support specifying `tag` as part of source configuration

See #5

"out" step metadata generation causes an error when build param is a WAR file

In our pipelines we specify:

build: uaa-war/uaa.war

And see this error:

fatal: cannot change to 'uaa-war/uaa.war': Not a directory

We believe this is coming from the metadata generation:

pack-concourse-resource/out

Line 104 in 422cad5

git: \"$(git -C $build rev-parse HEAD)\"

Note that the pack command and docker push do seem to work.

Re-release image with pack 0.3.0

$ docker run -ti --entrypoint "" bstick12/pack-concourse-resource pack version
v0.1.0 (git sha: e1793ab9fc3d172a416183ef3df20daf089eba19)

Could the image please be updated with pack 0.3.0?

Use the `registry-image-resource` for the check and in behaviours

https://github.com/concourse/registry-image-resource

ERRO[0000] failed to resolve name: could not parse reference

Any ideas why this resource might be failing after its successfully created the image?

build url https://ci2.starkandwayne.com/teams/drnic/pipelines/sample-app-nodejs/jobs/build-image/builds/9

When I run the resulting image it works just fine:

docker run -ti -p 8080:8080 starkandwayne/sample-app-nodejs

My simple pipeline to reproduce the error:

resources:
- name: git
  type: git
  source:
    uri: https://github.com/starkandwayne/sample-app-nodejs.git
- name: image
  type: pack-image-resource
  source:
    password: ((docker-hub-password))
    repository: starkandwayne/sample-app-nodejs:latest
    username: ((docker-hub-username))
resource_types:
- name: pack-image-resource
  type: docker-image
  source:
    repository: bstick12/pack-concourse-resource
  privileged: true
jobs:
- name: build-image
  plan:
  - get: git
    trigger: true
  - put: image
    params:
      build: git
      builder: cloudfoundry/cnb:cflinuxfs3