| commit | 19eab9efa1317f4086d95adaa94d57378dc82075 | [log] [tgz] |
|---|---|---|
| author | David Munro <davidmunro@google.com> | Thu Jul 16 12:18:58 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Jul 21 23:58:39 2020 |
| tree | 90938f7452c83cac898948414faf2b2f39eb33a8 | |
| parent | 74ea274e778ba67de33aee6ef44fcec37ab9efa4 [diff] |
container-guest-tools: Create /var/log/journal journald will automatically log to this folder if it exists. Create it so journald logs to disk instead of in-memory only. BUG=chromium:1105367 TEST=Build, copy deb into Crostini, run it, check folder is created Change-Id: I1f2114a52ca28afc436e1a0ce005f16182feeede Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2303130 Reviewed-by: Fergus Dall <sidereal@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: David Munro <davidmunro@google.com> Auto-Submit: David Munro <davidmunro@google.com>
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.