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

Compose fails due to an invalid Lighthouse image #2886

Closed
2 tasks
boulder225 opened this issue Feb 15, 2024 · 2 comments
Closed
2 tasks

Compose fails due to an invalid Lighthouse image #2886

boulder225 opened this issue Feb 15, 2024 · 2 comments
Assignees
Labels
protocol Protocol Team tickets

Comments

@boulder225
Copy link

boulder225 commented Feb 15, 2024

🎯 Problem to be solved

Compose fails during testing due to an invalid lighthouse image. Apparently, if you try pulling that image on an arm64 machine, docker won’t be able to do so because there’s no image for that arch.

🛠️ Proposed solution

  • Verify the integrity and compatibility of the lighthouse image.
  • Check if lighthouse changed their docker versioning tags
compose run
09:24:53.762 INFO run        Running compose command                  {"command": "run"}
09:24:53.763 INFO run        Created docker-compose.yml              
09:24:53.763 INFO run        Run the cluster with: docker compose up 
09:24:53.763 INFO run        Executing docker-compose build          
09:25:01.878 ERRO            Fatal error: exec docker compose build: exit status 17 {"output": "#0 building with \"laughing_lumiere\" instance using docker-container driver\n\n#1 [vc1-lighthouse internal] booting buildkit\n#1 pulling image moby/buildkit:buildx-stable-1\n#1 pulling image moby/buildkit:buildx-stable-1 5.5s done\n#1 creating container buildx_buildkit_laughing_lumiere0\n#1 creating container buildx_buildkit_laughing_lumiere0 0.6s done\n#1 DONE 6.1s\n\n#2 [vc1-lighthouse internal] load build definition from Dockerfile\n#2 transferring dockerfile: 368B done\n#2 DONE 0.0s\n\n#3 [vc1-lighthouse internal] load metadata for docker.io/sigp/lighthouse:latest-amd64-unstable-dev\n#3 ...\n\n#4 [vc1-lighthouse auth] sigp/lighthouse:pull token for registry-1.docker.io\n#4 DONE 0.0s\n\n#3 [vc1-lighthouse internal] load metadata for docker.io/sigp/lighthouse:latest-amd64-unstable-dev\n#3 ERROR: no match for platform in manifest: not found\n------\n > [vc1-lighthouse internal] load metadata for docker.io/sigp/lighthouse:latest-amd64-unstable-dev:\n------\nfailed to solve: sigp/lighthouse:latest-amd64-unstable-dev: no match for platform in manifest: not found\n"}
        testutil/compose/auto.go:211 .execUp
        testutil/compose/auto.go:271 .func1
        testutil/compose/compose/main.go:73 .func1
        testutil/compose/compose/main.go:31 .main
Error: exec docker compose build: exit status 17
Usage:
  compose run [flags]

Flags:
      --compose-dir string     Directory to use for compose artifacts (default ".")
  -h, --help                   help for run
      --up docker compose up   Execute docker compose up when compose command completes (default true)
@github-actions github-actions bot added the protocol Protocol Team tickets label Feb 15, 2024
@gsora
Copy link
Collaborator

gsora commented Feb 15, 2024

The compose command was probably run on an M1 Mac, which is an arm64 platform.

The docker image that you're trying to use is latest-amd64-unstable-dev, which as the name implies, only runs on amd64 platforms.

It appears that lodestar and lighthouse select amd64 images by default, while the tool should select the best one considering the platform on which it is executed.

This is due to the fact that developers assumed lighthouse/lodestar tests would only be executed on Github Actions, which are amd64 platforms.

This ticket needs a size and must be scheduled for fix.

obol-bulldozer bot pushed a commit that referenced this issue Feb 26, 2024
Supporting arm64 arch for `compose` tool.

category: feature
ticket: #2886
@pinebit pinebit self-assigned this Feb 26, 2024
@pinebit
Copy link
Contributor

pinebit commented Feb 26, 2024

Fixed

@pinebit pinebit closed this as completed Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

4 participants