I am actually confused on which engine | Dagger | Page 1

pseudo bramble Oct 9, 2024, 8:36 AM

#

hello @left pendant 👋
My understanding is that it's one or the other.
But, when preparing for KCD, I tried with both and found (with @sharp cairn help) that for my use case, connecting to the dagger engine installed with Helm worked better. You just need to adapt your argo-workflow to connect to the engine (attached below)
But for debugging, can you sh into the alpine container and see if the dagger.socket is there?

pseudo bramble Oct 9, 2024, 9:25 AM

#

📎 argo-sensor.txt

left pendant Oct 9, 2024, 3:32 PM

#

pseudo bramble hello <@1229793323535831050> 👋 My understanding is that it's one or the other....

I did this and the folder /var/run/dagger is indeed empty

left pendant Oct 9, 2024, 4:13 PM

#

@pseudo bramble your suggestion worked (removed the sidecar). I will revisit the sidecar later though

#

thanks

dry oriole Oct 9, 2024, 4:15 PM

#

Thanks for pointing that out @left pendant . The snippets in that argo workflows page are intended to use sidecars and not the helm chart

left pendant Oct 9, 2024, 4:23 PM

#

I think with the sidecars option, there is a change in the latest Argo Workflow v3.5.11 that requires to set the command:

error in entry template execution: failed to look-up entrypoint/cmd for image "registry.dagger.io/engine:v0.13.3", you must either explicitly specify the command, or list the image's command in the index: https://argo-workflows.readthedocs.io/en/release-3.5/workflow-executors/#emissary-emissary: secrets "image-pull-secret" is forbidden: User "system:serviceaccount:argo-workflows:argo-worklows-argo-workflows-workflow-controller" cannot get resource "secrets" in API group "" in the namespace "workflows"

pseudo bramble Oct 9, 2024, 4:24 PM

#

@left pendant, I tried to repro the same error, but I can get the workflow running with the sidecar container and no dagger engine installed with Helm.
But glad you were able to unblock the issue

left pendant Oct 9, 2024, 4:25 PM

#

which argo workflow version?

pseudo bramble Oct 9, 2024, 4:27 PM

#

left pendant which argo workflow version?

Chart: argo-workflows-0.42.2
App: v3.5.1

left pendant Oct 9, 2024, 4:29 PM

#

I have 0.42.5

#

App: v3.5.11

#

and it fails if I dont pass a command this way

#

Do you think the sidecars add any significant performance overhead?

pseudo bramble Oct 9, 2024, 4:57 PM

#

left pendant and it fails if I dont pass a command this way

Updated argo-workflows to:
argo-workflows-0.42.5 v3.5.11
and managed to still run the workflow
could there be a misconfiguration with your serviceAccount?

dry oriole Oct 9, 2024, 4:58 PM

#

I wouldn't say significant but it depends. The nice thing about having both options is that some teams don't have the authority to run dagger's helm chart in their cluster but would be able to run sidecars

#I am actually confused on which engine