We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Scenario:
batfish
allinone
Do not want to cut a new release (new Java), but rather re-release (and overwrite? bump? existing tag) allinone container only(?)
The text was updated successfully, but these errors were encountered:
https://buildkite.com/batfish/batfish-vulnerability-scan/builds/721#387ca25c-414d-42d7-9c80-ea33dded1ed1
Sorry, something went wrong.
Maybe, for current latest=2022.03.16.1242 we would generate tag 2022.03.16.<new build number and then overwrite latest with it.
2022.03.16.1242
2022.03.16.<new build number
latest
One manual hack is something like this:
cat allinone-upgrade.dockerfile
FROM batfish/allinone:<version> RUN apt-get update \ && apt-get upgrade -y \ && apt-get clean \ && rm -rf /var/lib/apt/lists/* \ && pip3 install --upgrade pillow
and then push this as latest or version. Iterated, however, this will result in a growing container as each time you do this it adds a new layer.
version
No branches or pull requests
Scenario:
batfish
container has no security issuesallinone
container, because it uses libc and other things like that, has security issuesDo not want to cut a new release (new Java), but rather re-release (and overwrite? bump? existing tag) allinone container only(?)
The text was updated successfully, but these errors were encountered: