Creating Cloud Native Buildpacks

Buildpacks have been the successful method for creating container images for a decade at Heroku and Cloud Foundry, before Dockerfiles existed. Cloud Native Buildpacks https://buildpacks.io are the latest set of tools and buildpacks to bring Buildpack methods for creating fast, secure images from your application source code.

In this talk I look at how to create new Cloud Native Buildpacks, how to test them, and how to distribute Builders for development teams to start using your buildpacks.

Transcript

1. Title Text Body Level One Body Level Two Body Level Three Body Level Four Body Level Five Creating
 Cloud Native Buildpacks Cloud Foundry Summit Hague 2019 Dr Nic Williams @drnic
2. @drnic Nothing should change for CF users EXCEPT This is about future v3 buildpacks WARNING
3. @drnic History v2 - Supply and Finalize CF own buildpacks evolved API Cloud Foundry had no buildpacks v1 - Heroku Buildpacks Borrowed API; offline buildpacks Ɲ v3 - Cloud Native Buildpacks Heroku and CF work together CNCF Incubator project Buildpacks are going everywhere
4. Cloud Foundry buildpacks thanks to…
6. @drnic Example NodeJS $ pack build starkandwayne/sample-app-nodejs [detector] ======== Results ======== [detector] pass: Node Engine Buildpack [detector] pass: Yarn Buildpack … [builder] -----> Node Engine Buildpack 0.0.26 [builder] Node Engine 10.16.2: [builder] Downloading from … … [builder] Process types: [builder] web: yarn start $ docker run -ti -p 8080:8080 \ starkandwayne/sample-app-nodejs
7. @drnic Example Spring $ pack build starkandwayne/sample-app-java ===> DETECTING [detector] skip: org.cloudfoundry.archiveexpanding@1.0.0-RC02 [detector] pass: org.cloudfoundry.openjdk@1.0.0-RC02 [detector] pass: org.cloudfoundry.buildsystem@1.0.0-RC02 [detector] pass: org.cloudfoundry.jvmapplication@1.0.0-RC02 [detector] pass: org.cloudfoundry.tomcat@1.0.0-RC02 [detector] pass: org.cloudfoundry.springboot@1.0.0-RC02 [detector] skip: org.cloudfoundry.jdbc@1.0.0-RC02 [detector] skip: org.cloudfoundry.jmx@1.0.0-RC02 [detector] Resolving plan... (try #1) [detector] Success! (7) … [builder] Cloud Foundry OpenJDK Buildpack 1.0.0-RC02 [builder] OpenJDK JDK 11.0.4: Contributing to layer $ docker run -ti -p 8080:8080 \ starkandwayne/sample-app-java
8. @drnic Deploy CF $ docker push starkandwayne/sample-app-nodejs $ cf push myapp \ -o starkandwayne/sample-app-nodejs \ -k 1536M $ cf logs my-node-app --recent
9. @drnic Buildpack API bin/detect Could this buildpack help this app? What requirements did we learn? ? bin/build Install dependencies Setup configuration Processes to launch #
10. @drnic Builder $ pack inspect-builder cloudfoundry/cnb Run Images: cloudfoundry/run:full-cnb Buildpacks: org.cloudfoundry.node-engine org.cloudfoundry.npm org.cloudfoundry.yarn org.cloudfoundry.python org.cloudfoundry.pip …
11. @drnic Ordered Groups $ pack inspect-builder cloudfoundry/cnb … Group #2: org.cloudfoundry.node-engine@0.0.44 org.cloudfoundry.yarn@0.0.23 Group #3: org.cloudfoundry.node-engine@0.0.44 org.cloudfoundry.npm@0.0.28 Group #4: org.cloudfoundry.python@0.0.19 org.cloudfoundry.pipenv@0.0.13 (optional) org.cloudfoundry.pip@0.0.19 …
12. @drnic 1, 2, 3, 4, 5, 6, 7, …, 15 FIZZ BUZZ 1, 2, fizz, 4, buzz, fizz, 7, …, fizzbuzz https://github.com/starkandwayne/fizzbuzz-cnb-builder
13. $ echo 1 > Count $ pack build myapp --builder fizzbuzz $ docker run myapp 1 $ echo 3 > Count $ pack build myapp --builder fizzbuzz $ docker run myapp fizz $ echo 15 > Count $ pack build myapp --builder fizzbuzz $ docker run myapp fizzbuzz https://github.com/starkandwayne/fizzbuzz-cnb-builder
14. @drnic FizzBuzz Buildpack bin/detect Does this app contain Count? ? bin/build Create executable to print Count or fizz, buzz, or fizzbuzz #
15. # bin/detect [ -f Count ]] || { echo "No Count file"; exit 1; } # bin/build cp -r $buildpack_dir/layer/* $layer_dir/ !"" fizzbuzz # $"" bin # $"" display-count !"" fizzbuzz.toml $"" launch.toml https://github.com/starkandwayne/fizzbuzz-cnb-builder
16. # launch.toml [[processes]] command = "display-count" type = "web" # fizzbuzz.toml launch = true # fizzbuzz/bin/display-count #!/bin/bash count=$(cat Count) if [[ $(( $count % 15 )) == "0" ]]; then echo "fizzbuzz" elif [[ $(( $count % 5 )) == "0" ]]; then echo "buzz" elif [[ $(( $count % 3 )) == "0" ]]; then echo "fizz" else echo $count fi% https://github.com/starkandwayne/fizzbuzz-cnb-builder layer metadata layer contents
17. $ pack build app \ --buildpack path/to/fizzbuzz \ --path to/app ===> DETECTING [detector] ======== Results ======== [detector] pass: fizzbuzz-standalone@1.0.0 [detector] Resolving plan... (try #1) [detector] Success! (1) ===> BUILDING [builder] ---> FizzBuzz Buildpack ===> EXPORTING [exporter] *** Images: [exporter] …playtime:latest - succeeded
18. @drnic Print Message Buildpack bin/detect Does this app contain Message? ? bin/build Create executable to print Message #
19. $ rm Count $ echo "Hello World" > Message $ pack build myapp --builder fizzbuzz $ docker run myapp Hello World $ rm Count $ rm Message $ pack build myapp --builder fizzbuzz <error>
20. # bin/detect [ -f Message ]] || { echo "No Message file"; exit 1; } # bin/build cp -r $buildpack_dir/layer/* $layer_dir/ !"" launch.toml !"" print-message # !"" bin # # !"" display-message # # $"" show-message-twice # $"" profile.d # $"" message.sh $"" print-message.toml
21. $ pack build app \ --buildpack path/to/print-message \ --path to/app ===> DETECTING [detector] ======== Results ======== [detector] pass: print-message@1.0.0 [detector] Resolving plan... (try #1) [detector] Success! (1) ===> BUILDING [builder] ---> Print Message Buildpack ===> EXPORTING [exporter] *** Images: [exporter] …playtime:latest - succeeded
22. @drnic FizzBuzz Builder # builder.toml [[buildpacks]] id = "fizzbuzz" uri = "buildpacks/fizzbuzz" [[buildpacks]] id = "print-message" uri = "buildpacks/print-message" …
23. @drnic FizzBuzz Builder # builder.toml … [[order]] [[order.group]] id = "fizzbuzz" [[order]] [[order.group]] id = "print-message" …
24. @drnic FizzBuzz Builder # builder.toml … [stack] id = "io.buildpacks.stacks.bionic" build-image = "cloudfoundry/build:base-cnb" run-image = "cloudfoundry/run:base-cnb"
25. @drnic FizzBuzz Builder $ pack create-builder fizzbuzz -b builder.toml Creating builder fizzbuzz from build-image cloudfoundry/build:base-cnb $ pack build myapp --builder fizzbuzz Count app Message app Runnable OCI/docker image
26. @drnic FizzBuzz Builder $ pack inspect-builder fizzbuzz Run Images: cloudfoundry/run:base-cnb Buildpacks: com.starkandwayne.fizzbuzz com.starkandwayne.print-message Detection Order: Group #1: com.starkandwayne.fizzbuzz@1.0.0 Group #2: com.starkandwayne.print-message@1.0.0
27. @drnic Example NodeJS $ pack build starkandwayne/sample-app-nodejs [detector] ======== Results ======== [detector] pass: Node Engine Buildpack [detector] pass: Yarn Buildpack … [builder] -----> Node Engine Buildpack 0.0.26 [builder] Node Engine 10.16.2: [builder] Downloading from … … [builder] Process types: [builder] web: yarn start $ docker run -ti -p 8080:8080 \ starkandwayne/sample-app-nodejs
28. Nothing should change for CF users START MIGRATING Cloud Native (v3) buildpacks COMING SOON
29. @drnic CONTINUE TO FIZZBUZZ https://github.com/starkandwayne/fizzbuzz-cnb-builder https://buildpacks.io/docs/create-buildpack/