This repository has been archived by the owner on Nov 6, 2022. It is now read-only.
Releases: GoogleCloudPlatform/cos-customizer
Releases · GoogleCloudPlatform/cos-customizer
v20210721
Only remove customizer.service at shutdown time Removing a systemd unit file changes the behavior of the unit. In particular, the value of "TimeoutStartUSec" changes from "infinity" (desired) to "1m 30s" (not desired) when the unit file is deleted. Deleting customizer.service early in the preload process increases the risk of TimeoutStartUSec kicking in and killing customizer.service. To minimize this risk, let's only delete the unit file during system shutdown (the stop behavior of customizer.service is invoked at shutdown time). A test is added to ensure that the unit file is indeed deleted. The test can only be run on Ubuntu, because /etc is stateless on COS.
v20210720
Update to latest cos-gpu-installer Fixes an issue on M89 where rust toolchain elements were not properly stripped. Also add a GPU test for M89 to catch this sort of problem before release.
v20210714
Update cos-gpu-installer to latest version Fixes an issue where GPU builds fail if the standalone toolchain includes hard links to the rust standard library.
v20210615
update anthos-installer version to allow downloading of docker images
v20210412
Run unit tests with mtools installed We use mtools to copy data onto the CIDATA disk image (which is a vfat file system). Unit tests depend on mtools being installed in the environment. Let's install mtools in the release workflow so that unit tests pass there. We install mtools by building a local container in the cloud build job that is gcr.io/cloud-builders/bazel + mtools. We then use this container in place of gcr.io/cloud-builders/bazel.
v20210204
Update cos-customizer to use cos-gpu-installer v20210204
v20200929
Add support for passing in an nvidia installer For certain types of pre-release images, it is useful to be able to choose the exact nvidia installer that we build with. This change allows users to specify an nvidia installer in the 'install-gpu' step. The installer must be specified in the '-version' flag, and if an installer is specified, it must be available in the '-deps-dir' directory.
v20200901
Revert "Update cos-gpu-installer to version v20200701" This reverts commit 267abc750b8039ec5de494d5d8b1fe12aca53bf3. This change is causing GPU tests to fail.
v20200723
Updated WORKSPACE dependencies (#28) The extend-oem-parititon binary is now built by bazel. With the rules_pkg introduced to build the binary to data/builtin_build_context/, the dependencies and package versions in bazel WORKSPACE are updated.
v20200722
Make sure that a unit exists before stopping it. (#27) If we stop a unit that doesn't exist, `systemctl stop` will return a non-zero exit code, resulting in a failed build. This causes issues when we remove units in new milestones. We use `systemctl is-active` to determine if we need to stop the unit or not. This isn't the same thing as checking if the unit exists, but it's good enough in this case because we really only want to stop the unit if it is active.