Wolfi 101: Container Images for Cloud Native

Learn more about Wolfi: github.com/wol...
About Chainguard
Founded by the industry's leading experts on open source software, security and cloud native development, we are on a mission to make the software supply chain secure by default.
Where to find us:
Website: www.chainguard...
Twitter: / chainguard_dev
LinkedIn: / chainguard-dev
TikTok: / chainguard_dev

[@ajr_almeida]

Erika, are you from Brazil?

[@Alestrix76]

For those that try out what is seen at 31:00 and also run into troubles:
1) the path to the yaml needs to be stated absolute (/work/apko.yaml)
2) If you, like me, need to add the musl libc "so:libc.musl-x86_64.so.1" (as printed out with apk info --depends ) to the package list, you will run into issues as apko tries to build a multi-arch image. You need to add "--arch x86_64" to the build command line!

[@kinjalbasu1999]

What are the benefits of using an 'undistro' over a webassembly runtime?

[@kinjalbasu1999]

Instead of using YAML to define installed packages, it would be MUCH better to use a declarative language like what nix and guix use.

[@frozenintime]

It's still declarative... Also ignoring a build structure is rather hazardous

[@kinjalbasu1999]

@@frozenintime YAML is just a data structure. It doesn't have independent tooling to call itself a language (declarative or otherwise). Languages have many benefits like compiler/interpreter-specific optimizations, code reuse etc.