Closed Ay1000 closed 1 year ago
@lmangani do you have time to look into this?
this one is implemented by PR/MR: https://github.com/sipcapture/heplify-server/pull/502
Can we trigger a pipeline @lmangani so that 'https://hub.docker.com/r/sipcapture/heplify-server/tags' is updated ? or is it a scheduled/autotriggered pipeline?
Thanks
The narwhal bacons at midnight automatically but I can trigger an early build.... but actually that's not going to work unless we increase the release version....
The narwhal bacons at midnight automatically but I can trigger an early build.... but actually that's not going to work unless we increase the release version....
@lmangani, I understand. And for the release version there is probably a procedure you are following (?). Sorry i'm new to this project so not really familiar with the release procedures etc.
@lmangani Can we increase the release version?
We're adding a few optimizations and a new build will take a few days. You can build your own image locally to test.
We're adding a few optimizations and a new build will take a few days. You can build your own image locally to test.
Hi, what is the status of the optimizations? Can we have a release on docker hub?
Tested locally, it works.
Hi Guys,
Would it be a good idea if the Dockerfile would be extended with apk update & apk upgrade to ensure all used packages are updated to the latest version?
So: `FROM alpine:latest RUN apk --no-cache add ca-certificates
RUN apk update <--- add this RUN apk upgrade <--- add this`
Using the latest alpine will not automatically use the latest tools shipped with alpine:latest.
asking this because based on the current Dockerfile, two CVE's apply:
Let me know what you think.
Thanks