-
Notifications
You must be signed in to change notification settings - Fork 386
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
M1 Mac Trying to run DevContainer, Ruby installation error #1134
Comments
Hi, Since I rebuilt without cache, I'm guessing it destroyed the cached container, so I can't rollback to a previous working version? devcontainer.json:
Host Machine Specs:
Output Logs:
|
Same issue as above with the Java feature - cropped up yesterday with a dev container that's been working for months. UPDATE: this issue seems to be related to the latest version. If I use version 1.5.0 it works as expected: “ghcr.io/devcontainers/features/java:1.5.0”
|
@pawaitemadisoncollege - Great, rollback seems to be working! |
@mattkoch-bb have you tried other ruby versions? I recall having ruby installation issues on arm macs because there weren't published releases for my specific version and the build was failing, these were most easily solved just by upgrading to a later release. Try at least |
* Add JDK 22 support * bump patch version * removed exit added for debugging * added one condition before changing the JDK_DISTRO * version set to 21 and jdk_distro open fixed * failed test cases fixed * fixing install_type issue if not java * yum update with epel-release install * explicit test case writen to validate jdk 22 works fine * moved check_packages to the start * INSTALL_CMD moved to start * variable changed
Exactly the same issue here, cannot build devcontainer locally with this latest version of the java feature. I've reached out to the author of the commit - see above. |
Hi @samruddhikhandale , |
Anyone having the Ruby issue like the original post was about? 😅 |
Hi all, I've been debugging this for the better part of my morning and can't seem to figure it out. Because I'm not able to start the container I can't see the error itself that the logs are telling me to look at (e.g.
please read /usr/local/rvm/log/1727803064_ruby-2.7.6/install.log
) - any idea on how to do that, or what coiuld be going on here?I'm on an M1 Mac running Sonoma 14.3, and my devcontainer feature is using this ruby version
Log output:
The text was updated successfully, but these errors were encountered: