You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we have been using the popular ianw/quickchart docker image for a while now. Recently, we were alerted to a vulnerability in it that meant we had to fork and build the image ourselves, as it has not been updated in about a year.
I'm aware that the existing image is not managed by this repo - would you be interested in a PR setting up CI actions to build and push docker images into Docker Hub automatically? This would potentially increase the maintenance burden of the project (managing OS + system library upgrades), so I understand if it's not something you're interested in.
Thanks for your work on the project; let me know if the above is something you're interested in, or if I should look at setting up a new docker hub image of my own with the updates we've done.
The text was updated successfully, but these errors were encountered:
Hey @tommilligan, thanks for flagging this and sorry you had to go through the trouble of forking and building. I've just built and uploaded a Docker image (v1.8.1). I'd gladly accept a PR that sets up CI actions.
Hi, we have been using the popular ianw/quickchart docker image for a while now. Recently, we were alerted to a vulnerability in it that meant we had to fork and build the image ourselves, as it has not been updated in about a year.
I'm aware that the existing image is not managed by this repo - would you be interested in a PR setting up CI actions to build and push docker images into Docker Hub automatically? This would potentially increase the maintenance burden of the project (managing OS + system library upgrades), so I understand if it's not something you're interested in.
Thanks for your work on the project; let me know if the above is something you're interested in, or if I should look at setting up a new docker hub image of my own with the updates we've done.
The text was updated successfully, but these errors were encountered: