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

Improve Devnet Docker image platform handling #1322

Open
hugocaillard opened this issue Jan 22, 2024 · 0 comments
Open

Improve Devnet Docker image platform handling #1322

hugocaillard opened this issue Jan 22, 2024 · 0 comments
Assignees

Comments

@hugocaillard
Copy link
Collaborator

hugocaillard commented Jan 22, 2024

Context

The Devnet allows to configure the docker_platform setting, which by default is "linux/amd64".
Meaning that all ARM (including Apple Silicon users) may experience degraded experiences.

Screenshot 2024-01-22 at 13 34 11

Problem

  • Some images, such as the official postgres ones, are multi-platform, meaning that if Clarinet wasn't enforcing the platform, Docker would automatically use linux/arm64 image when it would make sense.
  • For most of our other images, we don't have other platform versions (only "linux/amd64")

Possible solution

  • By default, maybe Clarinet shouldn't have a default platform, so that docker can automatically pick the right image
  • We should build multi-platform images for our custom images (bitcoin-node, stacks-node, stacks-api, bitcoin-explorer, stacks-explorer)

Additional context

I heard about some issues while running the Nakamoto image emulated for arm64, it was mentioned during visio calls so I don't have much more context about that

@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Jan 22, 2024
@hugocaillard hugocaillard changed the title Imrpove Devnet Docker image platform handling Improve Devnet Docker image platform handling Jan 22, 2024
@smcclellan smcclellan moved this from 🆕 New to 📋 Backlog in DevTools Jan 22, 2024
@tippenein tippenein self-assigned this Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants