-
Notifications
You must be signed in to change notification settings - Fork 75
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
Are patch versions of liquibase docker images expected to be immutable? #355
Comments
hi @ashleyheath , can you provide more details on what broke? For context, the
This was because liquibase checks is built with graalvm and requires either a home dir or setting an env var. The simplest solution was to add the home dir for the liquibase user and re-ship All of our automated tests passed and our QA team verified the changes. To answer your question: no, we typically don't re-ship the same version except in rare scenarios like this. If you can provide more context on the issue you're facing we're happy to help. |
Hi @jnewton03, Thanks for taking a look! We use the liquibase image as a base image and install additional tooling on top to facilitate database connectivity. We were installing this (via bash) using What appears to happen post this update is that |
@ashleyheath are you using the standard or alpine tag? |
Standard. |
@ashleyheath prior to
That was the issue we ran into with liquibase checks. It would fail since there was no home directory because the
Can you share your dockerfile and perhaps I can be of some assistance? |
hi @ashleyheath , just following up to see if I can be of assistance or if this issue can be closed. Thanks! |
It appears that the image for 4.31.0 has been updated since it was originally pushed, which has in turn broken images that use it as a base.
Should we expect images referenced by patch version tags to change over time or is the intention that the most specific version number for a tag will always return the same artifact?
The text was updated successfully, but these errors were encountered: