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>
6 files changed
tree: 90938f7452c83cac898948414faf2b2f39eb33a8
  1. .gitignore
  2. LICENSE
  3. OWNERS
  4. PRESUBMIT.cfg
  5. README.md
  6. WORKSPACE
  7. cros-adapta/
  8. cros-apt-config/
  9. cros-debs/
  10. cros-garcon/
  11. cros-gpu-alpha/
  12. cros-gpu-buster/
  13. cros-gpu-stretch/
  14. cros-guest-tools/
  15. cros-host-fonts/
  16. cros-logging/
  17. cros-notificationd/
  18. cros-pulse-config/
  19. cros-sftp/
  20. cros-sommelier-config/
  21. cros-sommelier/
  22. cros-sudo-config/
  23. cros-systemd-overrides/
  24. cros-tast-tests/
  25. cros-ui-config/
  26. cros-wayland/
  27. docs/
  28. kokoro/
  29. lxd/
  30. mesa/
  31. scripts/
  32. termina/
README.md

cros-container-guest-tools

Overview

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.

Building

The guest packages can be built with Bazel.

bazel build //cros-debs:debs --host_force_python=py2

Releasing

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.