Ashna Mehrotra
Ashna Mehrotra
@0xDagal copa is based on buildkit. If there is a way to provide buildkit connection via Podman then this should be possible.
@0xDagal in the documentation you can find podman as a supported format to provide as a custom address: https://project-copacetic.github.io/copacetic/website/custom-address. You can use this approach to provide buildkit connection via podman.
@VivekSubr are you able to connect to the buildx instance outside of copa? would you also be able to share the image to try to reproduce this issue?
@VivekSubr yes Copa will time out if it unable to connect to dockerd rather than throw an error in order to try the connection. This seems to be related to...
@justusbunsi Do you mean using a CronJob to schedule Eraser's ImageJob or have an option to eliminate ImageJobs? Without ImageJobs we will not be able to schedule an eraser pod...
@justusbunsi got it, yes I think would be very useful!
closing for #1160
@lzhecheng you can change the cpu via `deploy.resources.requests.cpu` https://github.com/eraser-dev/eraser/tree/v1.4.0-beta.0/charts/eraser
@macedogm thanks for the contribution! Can we also add logic for updating all outdated packages in the case updates is nil? Also, it necessary to use `zypper` inside the tooling...
@macedogm that makes sense! We can try combining as you suggested - I think that would allow us to reuse a lot of the existing rpm functionality and just section...