Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image docker.io/envoyproxy/envoy-build-centos not available #2404

Closed
toaler opened this issue Jan 18, 2018 · 6 comments
Closed

Image docker.io/envoyproxy/envoy-build-centos not available #2404

toaler opened this issue Jan 18, 2018 · 6 comments
Labels
question Questions that are neither investigations, bugs, nor enhancements

Comments

@toaler
Copy link

toaler commented Jan 18, 2018

The following is failing to pull down envoy-build-centos image from docker.io.

$:~/git/envoy$ IMAGE_NAME=envoyproxy/envoy-build-centos ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.release'
Unable to find image 'envoyproxy/envoy-build-centos:52f6880ffbf761c9b809fc3ac208900956ff16b4' locally
Pulling repository docker.io/envoyproxy/envoy-build-centos
docker: Tag 52f6880 not found in repository docker.io/envoyproxy/envoy-build-centos.
See 'docker run --help'.

@sudeeptoroy
Copy link
Contributor

U can set "IMAGE_ID=latest" along with IMAGE_NAME as a work around

@mattklein123 mattklein123 added the question Questions that are neither investigations, bugs, nor enhancements label Jan 18, 2018
@mattklein123
Copy link
Member

Sometimes the build images don't all build correctly due to CI timeouts, etc. Using latest is probably a fine workaround per @sudeeptoroy. Going to close this out. Let us know if you have other questions.

@toaler
Copy link
Author

toaler commented Jan 21, 2018

Even using IMAGE_ID=latest doesn't work:

$ IMAGE_ID=latest IMAGE_NAME=envoyproxy/envoy-build-centos ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.release'
Unable to find image 'envoyproxy/envoy-build-centos:latest' locally
latest: Pulling from envoyproxy/envoy-build-centos
af4b0a2388c6: Pull complete
8e46f47b29c9: Pull complete
205ea7d760f4: Pull complete
0fc9716f7163: Pull complete
cb05888b805a: Pull complete
5b168941ee29: Pull complete
fcd14a268a89: Pull complete
Digest: sha256:0f9e58399a918d74f9d018d28521b99ff108866c87fa4ba80980dc5059eba2c7
Status: Downloaded newer image for envoyproxy/envoy-build-centos:latest
/usr/bin/id: cannot find name for user ID 50093
/usr/bin/id: cannot find name for group ID 50093
/usr/bin/id: cannot find name for user ID 50093
ENVOY_SRCDIR=/source
M WORKSPACE
M bazel/get_workspace_status
M tools/bazel.rc
HEAD is now at b904b8c... filters: remove deprecated type(). (#19)
building using 16 CPUs
gcc/g++ toolchain configured
bazel release build with tests...
Building...
INFO: $TEST_TMPDIR defined: output root default is '/build/tmp' and max_idle_secs default is '15'.
Extracting Bazel installation...
ERROR: error loading package '': Encountered error while reading extension file 'bazel/repositories.bzl': no such package '@envoy_api//bazel': Traceback (most recent call last):
File "/build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/bazel_tools/tools/build_defs/repo/git.bzl", line 69
_clone_or_update(ctx)
File "/build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/bazel_tools/tools/build_defs/repo/git.bzl", line 44, in _clone_or_update
fail(("error cloning %s:\n%s" % (ctx....)))
error cloning envoy_api:

  • cd /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external
  • rm -rf /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/envoy_api
  • git clone https://github.com/envoyproxy/data-plane-api /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/envoy_api
    fatal: unable to look up current user in the passwd file: no such user
    Unexpected end of command stream
    ERROR: error loading package '': Encountered error while reading extension file 'bazel/repositories.bzl': no such package '@envoy_api//bazel': Traceback (most recent call last):
    File "/build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/bazel_tools/tools/build_defs/repo/git.bzl", line 69
    _clone_or_update(ctx)
    File "/build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/bazel_tools/tools/build_defs/repo/git.bzl", line 44, in _clone_or_update
    fail(("error cloning %s:\n%s" % (ctx....)))
    error cloning envoy_api:
  • cd /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external
  • rm -rf /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/envoy_api
  • git clone https://github.com/envoyproxy/data-plane-api /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/envoy_api
    fatal: unable to look up current user in the passwd file: no such user
    Unexpected end of command stream
    INFO: Elapsed time: 3.961s
    FAILED: Build did NOT complete successfully (0 packages loaded)

@sudeeptoroy
Copy link
Contributor

Can u confirm if u r using the latest src code.. very recently user is created before the build..

@toaler
Copy link
Author

toaler commented Jan 21, 2018

My build was based on checking out v1.5.0. The goal was to build a 1.5.0 binary. I'm assuming I need to grab the appropriate centos image at the time v1.5.0 was built?

@sudeeptoroy
Copy link
Contributor

can you patch this to ur code and try once:
https://github.com/envoyproxy/envoy/pull/2379/files

jpsim added a commit that referenced this issue Nov 28, 2022
Signed-off-by: GitHub Action <[email protected]>

Co-authored-by: jpsim <[email protected]>
Signed-off-by: JP Simard <[email protected]>
jpsim added a commit that referenced this issue Nov 29, 2022
Signed-off-by: GitHub Action <[email protected]>

Co-authored-by: jpsim <[email protected]>
Signed-off-by: JP Simard <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions that are neither investigations, bugs, nor enhancements
Projects
None yet
Development

No branches or pull requests

3 participants