|author||David Munro <email@example.com>||Mon Dec 28 22:26:40 2020|
|committer||Commit Bot <firstname.lastname@example.org>||Tue Dec 29 22:11:43 2020|
container-guest-tools: Restart Garcon and notificationd on failure When garcon explodes we should restart it, since otherwise users can't connect to the container without restarting. Also restart notificationd while I'm at it, but since Sommelier and sftp already restart don't touch them. BUG=chromium:1162127 TEST=Manually modify cros-garcon.service with Restart=always Change-Id: I7ed9e5c86be24bfd2e7d8356f1be3a75cf9991ed Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2602303 Tested-by: David Munro <email@example.com> Tested-by: kokoro <firstname.lastname@example.org> Auto-Submit: David Munro <email@example.com> Reviewed-by: Nicholas Verne <firstname.lastname@example.org> Reviewed-by: David Munro <email@example.com> Commit-Queue: David Munro <firstname.lastname@example.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.