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

Add Alpine Container #9

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

Add Alpine Container #9

mpldr opened this issue Apr 6, 2022 · 3 comments

Comments

@mpldr
Copy link

mpldr commented Apr 6, 2022

NPM is pretty heavy, which can inflate the image store significantly when regularly updating it. An Alpine Container would probably reduce this issue significantly.

@scottmando2000
Copy link

I second this, but for a different reason, security vulnerabilities. Alpine containers are already security focused.

I have just ran the latest version of nginx proxy manager through the Trivy container scanner to see that there are almost 1000 active CVE's in the project.

https://trivy.dev/results/?image=jc21/nginx-proxy-manager:latest

@jc21

@jc21
Copy link
Member

jc21 commented Oct 20, 2022

History lesson, NPM was using Alpine for most of it's life but it became unreliable and I can't exactly remember why but the history is hidden in an issue somewhere.. The next smallest solution was debian-slim. The base image is using debian:buster-slim and that probably could be changed to bullseye to get some updates to outdated packages.

@scottmando2000
Copy link

Thanks for the response!

Moving to bullseye would probably be a good step, but would it be possible to have scheduled build to prevent latest from getting out of date?
I did see that the last publish date on the latest tag was 7 months ago, which is a bit concerning on the security side of things.

Thanks,
Scott

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

3 participants