common: Fix typo with docker image loading.

The typo shouldn't have had any effect -- the kokoro instance should
be invoking this code exactly once on a fresh device each time, so we'd
expect the load to occur exactly once which is what is currently
happening.

BUG=None
TEST=None

Change-Id: I5d274ca5489984898ce4a8855a6afde54a488e87
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/1915090
Reviewed-by: Benjamin Gordon <bmgordon@chromium.org>
Commit-Queue: David Riley <davidriley@chromium.org>
Tested-by: David Riley <davidriley@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
1 file changed
tree: efd19d33fcae1d26b2d5bbde81dc6af3abad1d44
  1. .gitignore
  2. COMMIT-QUEUE.ini
  3. LICENSE
  4. OWNERS
  5. PRESUBMIT.cfg
  6. README.md
  7. WORKSPACE
  8. cros-adapta/
  9. cros-apt-config/
  10. cros-debs/
  11. cros-garcon/
  12. cros-gpu-alpha/
  13. cros-gpu-buster/
  14. cros-gpu-stretch/
  15. cros-guest-tools/
  16. cros-notificationd/
  17. cros-pulse-config/
  18. cros-sftp/
  19. cros-sommelier-config/
  20. cros-sommelier/
  21. cros-sudo-config/
  22. cros-systemd-overrides/
  23. cros-tast-tests/
  24. cros-ui-config/
  25. cros-wayland/
  26. docs/
  27. kokoro/
  28. lxd/
  29. mesa/
  30. scripts/
  31. 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.