fix potential encoding issues in remote actions
The new docker image contains all en_*.UTF-8 locales to ensure Java (and other) actions produce the correct bytes. Bug: b/300624128 Test: Ran an android build and verified there are no encoding issues in metalava outputs. Change-Id: I89cd1b45ce3d8dc552c2afb859c1a5e221c5f238
This commit is contained in:
parent
c416ddd1cc
commit
e208e856fd
1 changed files with 1 additions and 1 deletions
|
@ -30,7 +30,7 @@ const (
|
|||
// DefaultImage is the default container image used for Android remote execution. The
|
||||
// image was built with the Dockerfile at
|
||||
// https://android.googlesource.com/platform/prebuilts/remoteexecution-client/+/refs/heads/master/docker/Dockerfile
|
||||
DefaultImage = "docker://gcr.io/androidbuild-re-dockerimage/android-build-remoteexec-image@sha256:582efb38f0c229ea39952fff9e132ccbe183e14869b39888010dacf56b360d62"
|
||||
DefaultImage = "docker://gcr.io/androidbuild-re-dockerimage/android-build-remoteexec-image@sha256:953fed4a6b2501256a0d17f055dc17884ff71b024e50ade773e0b348a6c303e6"
|
||||
|
||||
// DefaultWrapperPath is the default path to the remote execution wrapper.
|
||||
DefaultWrapperPath = "prebuilts/remoteexecution-client/live/rewrapper"
|
||||
|
|
Loading…
Reference in a new issue