Overriding 'entrypoint' in kubernetes backend does not work

[everflux]

Component

agent

Describe the bug

I have a workflow that specifies an entrypoint, during execution the following error is shown

Additional property entrypoint is not allowed

System Info

Woodpecker 2.3.0, docker.io/woodpeckerci/woodpecker-agent:v2.3.0

Additional context

Pipeline snippet

cache-baseimages:
    image: gcr.io/kaniko-project/warmer
    entrypoint:
    - /kaniko/warmer
    - --dockerfile=./Dockerfile

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

[anbraten]

related #3269

[vjm]

i am also interested in this -- i can't run buildpacks right now because this image doesn't have /bin/sh:

https://github.com/buildpacks/pack/blob/main/Dockerfile

Is there a workaround in the meantime?

[anbraten]

Is there a workaround in the meantime?

You would have to create a plugin from the underlying docker image as plugins are using predefined commands and entrypoints.

[zc-devs]

Is there a workaround in the meantime?

# wget https://raw.githubusercontent.com/buildpacks/pack/main/Dockerfile
# sed -i 's\FROM ${base_image}\FROM gcr.io/distroless/static:debug\' Dockerfile
# docker build -f Dockerfile .

😆