liftedinit / liftedinit/many-rs

Docker build is broken

Open
#419 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
6
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Bazel rules_docker is unmaintained and the docker build is broken.

```shell
INFO: From Action ubuntu_download.tar:
The image bazel/image:image already exists, renaming the old one with ID sha256:fe7a3960a97ee41f84c8045700d2e5bd671a42f02a64ee33dde10627dee1a7d7 to empty string
Loaded image: bazel/image:image
3f2acbb582aa8aa0433fa754a3c55516bd9303cd82b58413fde01a92fd3312e6
INFO: From ExtractImageId ubuntu_image.tar.unstripped:
Loaded image: bazel/image:image
ERROR: /home/fmorency/dev/many-rs/BUILD.bazel:78:13: Action ubuntu_image.tar failed: (Exit 1): config_stripper failed: error executing command (from target //:ubuntu_image) bazel-out/k8-opt-exec-2B5CBBC6-ST-625e526ca8a8/bin/external/io_bazel_rules_docker/docker/util/config_stripper '--in_tar_path=bazel-out/k8-fastbuild-ST-4a519fd6d3e4/bin/ubuntu_image.tar.unstripped' ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
Traceback (most recent call last):
File "/home/fmorency/.cache/bazel/_bazel_fmorency/969684084a638869459983ef80b2f023/sandbox/linux-sandbox/1191/execroot/__main__/bazel-out/k8-opt-exec-2B5CBBC6-ST-625e526ca8a8/bin/external/io_bazel_rules_docker/docker/util/config_stripper.runfiles/io_bazel_rules_docker/docker/util/config_stripper.py", line 248, in
sys.exit(main())
^^^^^^
File "/home/fmorency/.cache/bazel/_bazel_fmorency/969684084a638869459983ef80b2f023/sandbox/linux-sandbox/1191/execroot/__main__/bazel-out/k8-opt-exec-2B5CBBC6-ST-625e526ca8a8/bin/external/io_bazel_rules_docker/docker/util/config_stripper.runfiles/io_bazel_rules_docker/docker/util/config_stripper.py", line 47, in main
return strip_tar(args.in_tar_path, args.out_tar_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/fmorency/.cache/bazel/_bazel_fmorency/969684084a638869459983ef80b2f023/sandbox/linux-sandbox/1191/execroot/__main__/bazel-out/k8-opt-exec-2B5CBBC6-ST-625e526ca8a8/bin/external/io_bazel_rules_docker/docker/util/config_stripper.runfiles/io_bazel_rules_docker/docker/util/config_stripper.py", line 73, in strip_tar
(new_layer_name, new_diff_id) = strip_layer(os.path.join(tempdir, layer))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/fmorency/.cache/bazel/_bazel_fmorency/969684084a638869459983ef80b2f023/sandbox/linux-sandbox/1191/execroot/__main__/bazel-out/k8-opt-exec-2B5CBBC6-ST-625e526ca8a8/bin/external/io_bazel_rules_docker/docker/util/config_stripper.runfiles/io_bazel_rules_docker/docker/util/config_stripper.py", line 169, in strip_layer
with tarfile.open(name=path, mode='r') as it:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/tarfile.py", line 1805, in open
return func(name, "r", fileobj, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/tarfile.py", line 1871, in gzopen
fileobj = GzipFile(name, mode + "b", compresslevel, fileobj)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/gzip.py", line 174, in __init__
fileobj = self.myfileobj = builtins.open(filename, mode or 'rb')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpw65mkp7y/blobs/sha256/a2d6ae7d60c7cc87a85352f28cc47d0d253178aac2389a589f28254d510ec7e7'
Target //:start-ledger-cluster failed to build

```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with BUILD.bazel at line 78 and reproduce the failure for //:ubuntu_image or //:start-ledger-cluster using the reported Docker and Bazel output. Inspect the external io_bazel_rules_docker config_stripper entry point referenced in the traceback. Done means the Docker build completes successfully without the missing blob error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.