-
Notifications
You must be signed in to change notification settings - Fork 3k
Workaround for DB2 Dev Service not starting on Podman #51204
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: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
|
Looks like Max is having a little fun with infrastructure? |
|
We should also remove the guard on the test. Well, assuming the test now passes with podman, which I can't check locally. :) quarkus/extensions/jdbc/jdbc-db2/deployment/pom.xml Lines 117 to 136 in f442026
|
Thanks, I forgot about this. Done!
🎉 |
Status for workflow
|
Status for workflow
|
|
🎊 PR Preview 0b1ce00 has been successfully built and deployed to https://quarkus-pr-main-51204-preview.surge.sh/version/main/guides/
|

Fixes #33104, at least in the default case when there are no volume mounts. Which I suppose is good enough?
At the very least, this looks better than simply failing to start with cryptic errors.