-
Notifications
You must be signed in to change notification settings - Fork 530
Payara 6.2025.9 update #11827
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
base: develop
Are you sure you want to change the base?
Payara 6.2025.9 update #11827
Conversation
|
||
# This is a JSON list containing a flattened map of branch names and the latest non-rolling tag | ||
# Example: [ "v6.6=gdcc/base:6.6-noble-r1", "v6.5=gdcc/base:6.5-noble-r5", "v6.4=gdcc/base:6.4-noble-r12", "develop=gdcc/base:6.7-noble-p6.2025.3-j17" ] | ||
# Example: [ "v6.6=gdcc/base:6.6-noble-r1", "v6.5=gdcc/base:6.5-noble-r5", "v6.4=gdcc/base:6.4-noble-r12", "develop=gdcc/base:6.7-noble-p6.2025.9-j17" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Receiving this error for
mvn -Pct clean package docker:build docker:start
[ERROR] DOCKER> Unable to pull 'gdcc/base:6.8-noble-p6.2025.9-j17' : {"message":"failed to resolve reference "docker.io/gdcc/base:6.8-noble-p6.2025.9-j17": docker.io/gdcc/base:6.8-noble-p6.2025.9-j17: not found"} (Not Found: 404) [{"message":"failed to resolve reference "docker.io/gdcc/base:6.8-noble-p6.2025.9-j17": docker.io/gdcc/base:6.8-noble-p6.2025.9-j17: not found"} (Not Found: 404)]
I don't see this tag on https://hub.docker.com/r/gdcc/base/tags
What this PR does / why we need it: Updates to the newest Payara that has bug fixes/security updates
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: Follow the docs to setup a new machine and to upgrade an existing machine
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: