-
Notifications
You must be signed in to change notification settings - Fork 59
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
New Java SCC causing problems. #203
Comments
@crpotter fyi, this issue should be addressed prior to the next release of images. |
I've opened #204 to fix this. It assumes that we want to use the SCC in the OpenJ9 container as the base SCC layer and add OpenLiberty SCC layers on top. The IBM JDK does not (currently) ship with an SCC so for that case we'll maintain the old behaviour of building the OL SCC layers in the old |
FYI: currently the embedded SCC into the OpenJ9 containers has only root access (.scc directory too), so it may NOT be usable for a container launched as a non-root user. |
I think Websphere Liberty OpenJ9 images will have this same issue: https://github.com/WASdev/ci.docker/blob/master/ga/latest/kernel/Dockerfile.ubi.adoptopenjdk8 |
@ymanton It did not work for me. It did build differently, but still see. If I go to /opt/java/.scc I see: |
It did work for me with the command:
It does help that the current user belongs to 'root' group |
Note that there are 5 dockerfiles under
The first 3 are based on the non-official OpenJ9 image from adoptopenjdk and they have the embedded scc. |
Some news: permission for the .scc directory have been fixed at adoptopenjdk (AdoptOpenJDK/openjdk-docker#407) and we should expect a new image probably tomorrow. |
I am seeing this new error in the openliberty/daily image. I assume this will hit the official images also soon. There is work to do getting the new java shared class cache working with ours. This causes a decent regression for startup time.
I see this option: -Xshareclasses:name=openj9_system_scc,cacheDir=/opt/java/.scc,readonly,nonFatal
I have already talked to @ymanton about this.
The text was updated successfully, but these errors were encountered: