-
Notifications
You must be signed in to change notification settings - Fork 827
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
Docker container fails to start from version 76.24.0 onwards #2658
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/186740037 The labels on this github issue will be updated when the story is started. |
Hi, I was not aware, that cloudfoundry/uaa is still created in docker hub. The error reason is the JDK 17 upgrade in uaa.war but obviously not in docker container, e.g. Dockerfile @Tallicia @peterhaochen47 @hsinn0 Can you please check where the deployment to cloudfoundry/uaa:76.29.0 is located and also update the image file ? similar to https://github.com/pivotal/uaa-ci/commit/e946ae21fb76429b2d663b844df510ce18274882 Thanks |
The Dockerfile was deleted in #2422 because this was not used to create images in https://hub.docker.com/r/cloudfoundry/uaa/tags. |
Yes, there is a separate process (not Dockerfile based) creating and publishing https://hub.docker.com/r/cloudfoundry/uaa. We will discuss this issue at our next planning meeting. |
@kukumber Could you try again with the latest release (76.30.0)? |
I think still 11 inside the image -> docker inspect cloudfoundry/uaa:76.30.0 Find "io.paketo.stacks.tiny","*"],"uri":"https://github.com/bell-sw/Liberica/releases/download/11.0.21+10/bellsoft-jre11.0.21+10-linux-amd64.tar.gz\",\"version\":\"11.0.21\"}} And tomcat 9.0.83 is inside instead of expected 9.0.85 |
Looking into it again |
@peterhaochen47 I checked with version 76.30.0 just in case. I see the same error. |
I've checked the version 76.31.0, the issue still persists. |
Just tried |
@peterhaochen47 Yes, I've checked version 77.0.0, the container starts without errors. Thank you. |
Hi @kukumber, could we ask about your use case of this docker image? And are you using it as part of some larger product? |
Hi @peterhaochen47, unfortunately, I can't disclose details of the services because of an NDA. I can only say that it's part of an internal infrastructure. |
I see. We are asking because we plan to soon stop publishing the image; the reason is that there appears to be very limited usage of it & that the hosted service we use to build the image is being sunset as well. If you still need it, you can build the image yourself. We were using kpack to build it (for which we could share the kpack configs); or you could write a tranditional Dockerfile. |
Oh, I got it. I would appreciate it if you could share the kpack configs. |
Hi all! I would also have interest in the kpack files. :) |
I'm encountering an issue where I can't run the Docker container starting from version 76.24.0.
With version 76.23.0, the container starts without any issues. I've been using the following command:
However, starting from version 76.24.0, the container crashes with the following error:
I've tested all available versions from 76.24.0 to 76.29.0 and encountered the same issue.
Any assistance in resolving this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: