commit | 216f2f5fb1f8e4c3003afabf746486b5c1dad589 | [log] [tgz] |
---|---|---|
author | Fergus Dall <sidereal@google.com> | Mon May 10 07:24:27 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Tue May 11 01:12:53 2021 |
tree | 390757cfd083b074cf490b54456f232afafa85b1 | |
parent | 4669dde01970d897fff2c4e2b7a1cfa00d6e6954 [diff] |
termina_build_image: Call unsquashfs with -no-xattrs The newest version of squashfs-tools considers failing to write xattrs (say, because you are not root) a fatal error. Since this never worked before, it's probably fine to just turn that off. BUG=b:186436472 TEST=manually tested Change-Id: I791c6d17790da5f43195ac90711295860b14cbc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2881526 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Fergus Dall <sidereal@google.com> Reviewed-by: David Munro <davidmunro@google.com> Reviewed-by: Nicholas Verne <nverne@chromium.org>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.