-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Update dev service docker image versions #42078
Conversation
LGTM, @loicmathieu @yrodiere do you want to take a look as well? Thanks |
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.
LGTM, but we'll need an entry in the migration guide, similar to what I suggested in #41507 (comment)
build-parent/pom.xml
Outdated
<oracle.image>docker.io/gvenzl/oracle-free:23-slim-faststart</oracle.image> | ||
<mongo.image>docker.io/mongo:4.4</mongo.image> | ||
<mongo.image>docker.io/mongo:7.0.12</mongo.image> |
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.
I think that 7.0 should be used as it seems to point to latest 7.0.x.
Tested it with docker run --name some-mongo -d mongo:7.0
and see that 7.0.12 version is used.
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.
Push changed to 7.0
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.
I added a note here: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.14
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.
LGTM, no sure why we use a so old image for Mongo but I remember some issue with some images not available on arm64.
This comment has been minimized.
This comment has been minimized.
Something changed in PostgreSQL, I would bet:
|
@gsmet i downgraded to PG 15 as it looks like Flyway only supports 15 for now: flyway/flyway#3743 |
This comment has been minimized.
This comment has been minimized.
I wonder if we have to update Flyway version too or i should just leave Postgres at 14? |
@melloware looking at postgres release notes. They done
I think one of this is responsible for that error. Maybe it's the bug in Flyway. |
I think we can do the latter as a first step |
Yeah I suspect we just have to update our tests to not use the public schema and to create a schema ourselves. It's good practice anyway. So if you have time, please do it and upgrade to latest, I would expect it to work. If you don't, you can drop the PostgreSQL update. |
For now @gsmet i backed up to 14. Should I open another ticket so we can track updating to PG 16? |
Sure: please add all the details about the problem we have with Flyway. |
This comment has been minimized.
This comment has been minimized.
I suspect the failure to download Redis is unrelated. I rebased on main to trigger another run on a more up-to-date codebase... Let's see how it goes. |
Status for workflow
|
Merged, thanks! FTR, the issue about Postgres 16: #42149 |
Fix #42045