Skip to content
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

allinone: want ability to upgrade base container #82

Open
dhalperi opened this issue Apr 6, 2022 · 3 comments
Open

allinone: want ability to upgrade base container #82

dhalperi opened this issue Apr 6, 2022 · 3 comments

Comments

@dhalperi
Copy link
Member

dhalperi commented Apr 6, 2022

Scenario:

  • batfish container has no security issues
  • allinone container, because it uses libc and other things like that, has security issues

Do not want to cut a new release (new Java), but rather re-release (and overwrite? bump? existing tag) allinone container only(?)

@dhalperi
Copy link
Member Author

dhalperi commented Apr 6, 2022

Maybe, for current latest=2022.03.16.1242 we would generate tag 2022.03.16.<new build number and then overwrite latest with it.

@dhalperi
Copy link
Member Author

dhalperi commented Jun 6, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant