Skip to content

Latest commit

 

History

History
69 lines (59 loc) · 2.3 KB

tricks.md

File metadata and controls

69 lines (59 loc) · 2.3 KB
Raw

Tips and Tricks

Building a layer from scratch

There are a couple of cases where it may be useful to build a layer from scratch. For example to derive a new base install of an OS or to build a "tarball" type image which just carries data and will not actually be run by a container runtime.

The way to accomplish this in stacker is to use a build only layer (i.e. a layer that does not get emitted into the final OCI image, perhaps containing assets or something that will be used by the final container).

The best way to accomplish this is as follows:

build:
    from:
        type: docker
        url: docker://ubuntu:latest
    run: |
        touch /tmp/first
        touch /tmp/second
        tar -C /tmp -cv -f /contents.tar first second
    build_only: true
contents:
    from:
        type: tar
        url: stacker://build/contents.tar

Or e.g. to bootstrap a base layer for CentoOS 7:

build:
    from:
        type: docker
        url: docker://ubuntu:latest
    run: |
        yum -y --installroot=/rootfs --nogpgcheck install
        tar -C rootfs -zcf /rootfs.tar .
    build_only: true
contents:
    from:
        type: tar
        url: stacker://build/rootfs.tar

These work by creating the base for the system in a build container with all the utilities available needed to manipulate that base, and then asking stacker to create a layer based on this tarball, without actually running anything inside of the layer (which means e.g. absence of a shell or libc or whatever is fine).

Another way to accomplish something similar is to use a distroless layer:

build:
    from:
        type: docker
        url: docker://ubuntu:latest
    binds:
        - /tmp/dir_to_overlay -> /dir_to_overlay
    run: |
        touch /dir_to_overlay/binaryfile
    build_only: true
contents:
    from:
        type: docker
        url: docker://gcr.io/distroless/base
    overlay_dirs:
        - source: /tmp/dir_to_overlay
          dest: /dir_to_overlay

You can use the first layer as a build env, and copy your binary to a bind-mounted folder. Use overlay_dirs with that same folder to have the binary in the distroless layer.