use envoy-build-ubuntu image build error

[headshot289]

I tried to compile with envoyproxy/envoy-build-ubuntu image, but I encountered some errors..

The following is the terminal output

root@99159dbae7b0:/source# ./ci/do_ci.sh bazel.dev
No remote cache bucket is set, skipping setup remote cache.
ENVOY_SRCDIR=/source
start setup_clang.sh
$TEST_TMPDIR defined: output root default is '/build/tmp' and max_idle_secs default is '15'.
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/source/tools/bazel.rc
Starting local Bazel server and connecting to it...
LLVM_PREFIX = /opt/llvm
BAZELRC_FILE = /source/clang.bazelrc
HEAD is now at 03b4593... remove v1 methods (#108)
building using 4 CPUs
clang toolchain with libc++ configured
bazel fastbuild build with tests...
Building...
Building...
$TEST_TMPDIR defined: output root default is '/build/tmp' and max_idle_secs default is '15'.
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/source/tools/bazel.rc
INFO: Analyzed target //source/exe:envoy-static (428 packages loaded, 19365 targets configured).
INFO: Found 1 target...
INFO: Deleting stale sandbox base /build/tmp/_bazel_bazel/b570b5ccd0454dc9af9f65ab1833764d/sandbox
INFO: From CcCmakeMakeRule external/envoy/bazel/foreign_cc/zlib/include [for host]:

ERROR: /build/tmp/_bazel_bazel/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:177:1: TreeArtifact external/envoy/bazel/foreign_cc/zlib/include was not created

ERROR: /build/tmp/_bazel_bazel/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:177:1: TreeArtifact external/envoy/bazel/foreign_cc/copy_zlib/zlib was not created

ERROR: /build/tmp/_bazel_bazel/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:177:1: not all outputs were created or valid

Target //source/exe:envoy-static failed to build
INFO: Elapsed time: 52.778s, Critical Path: 17.47s
INFO: 1 process: 1 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

[yanavlasov]

Do you have /build/tmp directory? Is it writable?

[headshot289]

Do you have /build/tmp directory? Is it writable?

@yanavlasov Thanks for your reply.

This directory exists and writable.

root@99159dbae7b0:/build/tmp# pwd
/build/tmp
root@99159dbae7b0:/build/tmp# ls -ll
total 0
drwxr-xr-x 5 root root 160 Oct 26 09:10 _bazel_bazel
drwxr-xr-x 5 root root 160 Oct 28 03:36 _bazel_envoybuild

[lizan]

Which image are you using and what version of Envoy are you trying to compile?

[headshot289]

Which image are you using and what version of Envoy are you trying to compile?

@lizan I used image is envoyproxy/envoy-build-ubuntu tag:b480535e8423b5fd7c102fd30c92f4785519e33a, Envoy on release/v1.16 branch

[smwyzi]

i met the same problem, @headshot289 ,have u found any solution?

[aakatev]

same error. do you guys have any advice?

[aakatev]

Just tried to build it on Linux machine and it works fine. The issue persists on Mac Docker host on all the releases including 1.14-1.16.

[smwyzi]

i have to install virtualbox in my mac, then install ubuntu in virtualbox, then install docker in ubuntu, finally, build envoy in docker in ubuntu in virtualbox in mac ^ω^

[aakatev]

i have to install virtualbox in my mac, then install ubuntu in virtualbox, then install docker in ubuntu, finally, build envoy in docker in ubuntu in virtualbox in mac ^ω^

Interesting.

I wonder if there is some known and undocumented (or missed by me) reason why docker builds on mac hosts are failing.

[Edward-Gavin]

Same error in Mac, do you have other solution? @aakatev

[aakatev]

@li-guest I gave up trying to build on Mac. The solution is digging into this script. It was not worth it for me, since the build agents used for Envoy builds are running Linux.

[boringuy]

I got the same error when using docker on Mac. I am not familiar with the ci_build script but if it is using shared folder, changing the bazel_cache directory to directory inside the container will solve the problem. I modified my .bazelrc to add --output_user_root=/tmp/bazel_cache startup option.

[alandtsang]

Is there a solution?

Generating v2 API RST...
Starting local Bazel server and connecting to it...
INFO: Analyzed target @envoy_api_canonical//:v2_protos (300 packages loaded, 1938 targets configured).
INFO: Found 1 target...
INFO: From CcCmakeMakeRule external/envoy/bazel/foreign_cc/zlib/include:

ERROR: /build/.cache/bazel/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:219:21: TreeArtifact external/envoy/bazel/foreign_cc/zlib/include was not created
ERROR: /build/.cache/bazel/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:219:21: TreeArtifact external/envoy/bazel/foreign_cc/copy_zlib/zlib was not created
ERROR: /build/.cache/bazel/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/envoy/bazel/foreign_cc/BUILD:219:21: not all outputs were created or valid
Aspect //tools/protodoc:protodoc.bzl%protodoc_aspect of @envoy_api_canonical//:v2_protos failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 73.548s, Critical Path: 13.64s
INFO: 1 process: 1 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

[jstewmon]

I ran into this issue too. Having had problems with the gRPC FUSE file sharing feature in the past, I tried switching back to osxfs file sharing, and the problem vanished.

gRPC FUSE became the default in Docker Desktop Community 2.4.0.0 (released 2020-09-30). If you have a problem with a mounted volume using Docker for Mac, try switching back to osxfs.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.