jqplay Dockerfile is using an unsupported setting (RUN --mount) for Kaniko in orphaned stage gotest
While I admit the issue is on the Kaniko side at the moment, I also wonder what the expectations are for such an orphaned build stage? Is it to break the build when gotest stage is unsuccessful? Is it a well-known pattern? Can't this be achieved outside of the Dockerfile?
As there is no way to skip a Dockerfile stage, the only solution to build the image on Kaniko at the moment is to alter the Dockerfile on the fly, removing the gotest stage. This is not very convenient.
jqplay Dockerfile is using an unsupported setting (
RUN --mount
) for Kaniko in orphaned stage gotestWhile I admit the issue is on the Kaniko side at the moment, I also wonder what the expectations are for such an orphaned build stage? Is it to break the build when
gotest
stage is unsuccessful? Is it a well-known pattern? Can't this be achieved outside of the Dockerfile?As there is no way to skip a Dockerfile stage, the only solution to build the image on Kaniko at the moment is to alter the Dockerfile on the fly, removing the
gotest
stage. This is not very convenient.Thank you