Unset entrypoint?

[frozen harness]

Hey, I've got a situation where I would like to "unset" the entrypoint provided by another image (to run tests). At this point, it doesn't seem like this is possible. I've tried setting it to a blank string and I've tried using /bin/bash -c and /bin/sh -c and nothing seems to get it to the blank slate again.

[tidal ether]

there is a container.withoutEntrypoint

[frozen harness]

ah I didn’t see it in the docs for the NodeJS SDK; is this new?

[tidal ether]

I don’t think so - but maybe it didn’t get shipped? let me check

[scarlet rune]

@tidal ether I don't recall having a WithoutEntrypoint. Having said that, setting the WithEntryPoint to something blank should work.

    digest, err := client.Container().From("nginx").
        WithEntrypoint([]string{"echo", "hello"}).
        WithDefaultArgs(dagger.ContainerWithDefaultArgsOpts{Args: []string{""}}).
        Publish(ctx, "ttl.sh/marcosnils:nginxtest")

^ that resets the entrypoint to "echo hello"

[tidal ether]

oh that’s what it was!

[solar crescent]

Fyi: https://github.com/dagger/dagger/issues/3284

[tidal ether]

I don't think that's right... Should be WithEntrypoint(nil) no? WithDefaultArgs is something else

[solar crescent]

Yep, WithEntrypoint(nil) and WithDefaultArgs(). for entrypoint and default args. If either one of those is set, it'll run as a default command.

[tidal ether]

I agree with that issue, WithEntrypoint(nil) is very confusing

[scarlet rune]

I just checked and WithEntrypoint(nil) doesn't do anything

[tidal ether]

I think technically it's WithEntrypoint([]string{})

The GraphQL spec doesn't allow a null args value

[scarlet rune]

WithEntrypoint([]string{}) also doesn't change it

[solar crescent]

Yeah, but the Go SDK has turned nil into the empty []string{} via marshaling. So in Go it should be equivalent.

[tidal ether]

https://play.dagger.cloud/playground/OT1N2qt9bZg

Seems to work

[solar crescent]

What's your repro?

[scarlet rune]

    digest, err := client.Container().From("nginx").
        WithEntrypoint([]string{}).
        Publish(ctx, "ttl.sh/marcosnils:nginxtest")

^ if you run that image afterwards, the nginx default entrypoint is kept

[scarlet rune]

wait, I got it wrong

[solar crescent]

docker inspect --format='{{json .Config.Entrypoint}}' ttl.sh/marcosnils:nginxtest
[""]

[scarlet rune]

yep, that's it. Thx Helder 🚀

[solar crescent]

Don't need the empty string. That's not empty args. It's a list with an empty value.

[tidal ether]

Oh, sorry I didn't check to see if the removed entrypoint is applied to a pushed image. Only tested with immediate execution

[solar crescent]

So WithEntrypoint([]string{}) rather than WithEntrypoint([]string{""}).

[scarlet rune]

yep :😊

[tidal ether]

docker pull ttl.sh/marcosnils:solomontest@sha256:9f7396c3c2e63e423153df613c434cfa0212523d7049c8c55c2dc23576cdda62

https://play.dagger.cloud/playground/Oxyz5bI-g3p

Side note: add a ttl.sh module to zenith 😛

[scarlet rune]

I keep doing tests so you might be getting inconsistent outputs 😬

but yes, both WithEntrypoint(nil) and WithEntrypoint([]string{}) will set the OCI spec to Entrypoint:null as Helder was correctly pointing out

@frozen harness let us know if this helps with your current issue and if you need further help 🙏

[solar crescent]

To reset the default args I believe all you need is WithDefaultArgs() since that argument is optional.

https://play.dagger.cloud/playground/28Vi9vVtnq8

[scarlet rune]

yep, indeed

[frozen harness]

ill give it a shot tomorrow

[frozen harness]

this worked:

.withEntrypoint([])

I'd expect to be able to pass null here (this is the Node SDK) to unset it; it makes sense when you think about it for a few minutes but it's a little counterintuitive when you are first encountering it.

Thanks for the help, I can reset it now.

@scarlet rune ^

[tidal ether]

@frozen harness thanks for the feedback, I agree. We should 1) support null and 2) add withoutEntrypoint IMO

[scarlet rune]

that makes sense @frozen harness ! glad you managed to make it work. Would you mind opening an issue in dagger/dagger so we can address the nil case? We accept contributions too 😛

[frozen harness]

sure, maybe ill be able to help out there

[frozen harness]

sorry that took a while, just added the issue