Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
eeeerp we (very likely, me) definitely messed up:
$ tar xvzf ./concourse-5.6.0-linux-amd64.tgz ./concourse/resource-types/cf/rootfs.tgz x concourse/resource-types/cf/rootfs.tgz $ tar xvzf ./concourse/resource-types/cf/rootfs.tgz ./usr/lib/os-release x ./usr/lib/os-release $ cat ./usr/lib/os-release NAME="Ubuntu" VERSION="18.04.2 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.2 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic
that should be alpine
Thinking about this, I wonder if we could actually get away from having the two base images and get back to a single one.
We added Ubuntu with the premise that we could then get Canonical support for what we had under the base image, having the major drawback that size would increase considerably, as well as number of files (very relevant for
More recently however, there's been the development of cloudfoundry/run:tiny which, as they say
giving us a very small base that we could leverage in most of the images. e.g., the latest version is at 7MB compressed: https://hub.docker.com/layers/cloudfoundry/run/tiny/images/sha256-59854a1770d0383f450ff29fdc259cb9d01a89c9921c8d55bf9231fd67d28242
This way we could get the best of both - support + small size.
ps.: I'm pretty sure this will not be the definitive solution for all of our images, but, I'm pretty sure it can handle most of them (the ones that are just pure go)
Going to the distroless is definitely going to be great for reducing size and attack surface vector.
We should also think about how we go about