Skip to content

Latest commit

 

History

History
62 lines (44 loc) · 2.78 KB

BUILD_FROM_SOURCE_README.md

File metadata and controls

62 lines (44 loc) · 2.78 KB
Raw

Source Code Notes

Pinning Bundled System Charts

The Rancher Dockerfile used to build the Rancher image uses git clone to embed Helm system charts in the image. The clone is done from a branch, but does not checkout a specific commit. There are commits to the Rancher partner chart repositories fairly regularly, which means every time we rebuild our forked Rancher image it could pull in a newer version of the system charts. This makes the Rancher image build nondeterministic with respect to the bundled system charts.

To fix this problem, we have modified the Dockerfile to checkout specific commits in the system chart repositories. When building a new version of Rancher from source, you must determine the commit ids that are used in the upstream Rancher image and set them in the Dockerfile. The easiest way to determine the commit ids is to run the upstream Rancher image interactively and use git

For example, to find the relevant chart git commits for v2.7.8:

The rancher charts commit below must be updated from the latest commit on the Verrazzano fork of the rancher charts BFS oracle/release/2.7.8 branch.

$ docker run --privileged -it --entrypoint=bash rancher/rancher:v2.7.8

de667f186d5d:/var/lib/rancher # git -C /var/lib/rancher-data/local-catalogs/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721 rev-parse HEAD
f63f05431cdb2d969b550174d6427d3a571b6e95

Build Instructions

The upstream tag this release is branched from the release tag v2.7.8

BFS chart Updates for release v2.7.8

Verrazzano requires the BFS of the below image versions to be updated in the verrazzano-bom.json file to support rancher v2.7.8.

  • Rancher webhook - v0.3.6
  • Rancher backup and restore operator - v3.1.0
  • Rancher fleet - v0.8.0
  • Rancher fleet-agent - v0.8.0
  • Rancher gitjob - v0.3.2
  • kubectl - v0.25.4

Create Environment Variables

export DOCKER_REPO=<Docker Repository>
export DOCKER_NAMESPACE=<Docker Namespace>
export DOCKER_TAG=<Docker Tag>

Build and Push Images

By default, Rancher uses the latest tag on the Git branch as the image tag, so create the tag and run make:

git tag ${DOCKER_TAG}
make

Alternatively you can skip creating the tag and simply pass an environment variable to make:

TAG=${DOCKER_TAG} make

Once the build completes successfully, tag and push the images:

docker tag rancher/rancher:${DOCKER_TAG} ${DOCKER_REPO}/${DOCKER_NAMESPACE}/rancher:${DOCKER_TAG}
docker tag rancher/rancher-agent:${DOCKER_TAG} ${DOCKER_REPO}/${DOCKER_NAMESPACE}/rancher/rancher-agent:${DOCKER_TAG}
docker push ${DOCKER_REPO}/${DOCKER_NAMESPACE}/rancher:${DOCKER_TAG}
docker push ${DOCKER_REPO}/${DOCKER_NAMESPACE}/rancher/rancher-agent:${DOCKER_TAG}