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

Graalvm docker image repository no longer hosted at docker hub #1394

Closed
kgston opened this issue Jan 22, 2021 · 4 comments · Fixed by #1395
Closed

Graalvm docker image repository no longer hosted at docker hub #1394

kgston opened this issue Jan 22, 2021 · 4 comments · Fixed by #1395
Labels
bug graalvm GraalVM releated issues

Comments

@kgston
Copy link
Contributor

kgston commented Jan 22, 2021

The docker hub page now returns 404: https://hub.docker.com/r/oracle/graalvm-ce
Seems like it was migrated sometime back to Github container repository at ghcr.io/graalvm/graalvm-ce https://github.com/orgs/graalvm/packages/container/package/graalvm-ce

@muuki88
Copy link
Contributor

muuki88 commented Jan 23, 2021

Thanks a lot for brining this up 😊. I don't use the graalvm feature ( yet ). IIRC this is related to the build process itself, right?

I'm happy to merge any pull requests on this 🤗

cc @ScalaWilliam

@ScalaWilliam
Copy link
Contributor

Thanks for checking with me @muuki88!

I think the Docker usage for GraalVM was introduced in #1251 by @jroper, are you by any chance able to look at this? I would love to look into it but my bandwidth is currently very limited.

@kgston
Copy link
Contributor Author

kgston commented Jan 24, 2021

Yes, this is used when building a native image in a Graalvm docker image. I actually took a look at the potential fix, and I think it would be a quick name change here:

The fix worked, but I couldn't figure out why the Graalvm test wouldn't pass... Something along the lines of output test native-image binary couldn't find the Main class. I haven't looked too deeply into what was causing the issue.

Currently I'm just working around the whole issue by using the setting (containerBuildImage in GraalVMNativeImage) := GraalVMNativeImagePlugin.generateContainerBuildImage(s"ghcr.io/graalvm/graalvm-ce:java11-21.0.0").value
p.s. the instructions on the web documentation related to this option seems to be outdated, thankfully the code itself was commented with the right example.

/**
* This can be used to build a custom build image starting from a custom base image. Can be used like so:
*
* ```
* (containerBuildImage in GraalVMNativeImage) := generateContainerBuildImage("my-docker-hub-username/my-graalvm").value
* ```
*
* The passed in docker image must have GraalVM installed and on the PATH, including the gu utility.
*/

@muuki88
Copy link
Contributor

muuki88 commented Jan 25, 2021

Thanks @kgston for giving it a shot 🤗 You could open a pull request with the change, which seems quite right. Then some one can take a look and see what the issue is. If there's something weird going on with the sbt scripted test setup, I'll surely look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug graalvm GraalVM releated issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants