Tried out the Dagger DaemonSet Helm | Dagger | Page 1

the example is much simpler without the sidecar dagger

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: dagger-in-argo-
spec:
  entrypoint: dagger-workflow
  volumes:
    - name: dagger-socket-host
      hostPath:
        path: /run/dagger-dagger-dagger-helm
  templates:
    - name: dagger-workflow
      inputs:
        artifacts:
          - name: project-source
            path: /work
            git:
              # replace with your repository URL
              repo: https://github.com/kpenfound/greetings-api.git
              revision: "main"
          - name: dagger-cli
            path: /usr/local/bin
            mode: 0755
            http:
              # replace with the latest available version of Dagger for your platform
              url: https://github.com/dagger/dagger/releases/download/v0.18.8/dagger_v0.18.8_linux_amd64.tar.gz
      container:
        image: alpine:latest
        command: ["sh", "-c"]
        # modify to use different function(s) as needed
        args: ["dagger -m github.com/kpenfound/dagger-modules/golang@v0.2.0 call test --source=."]
        workingDir: /work
        env:
        - name: "_EXPERIMENTAL_DAGGER_RUNNER_HOST"
          value: "unix:///run/dagger/engine.sock"
          # assumes the Dagger Cloud token is
          # in a Kubernetes secret named dagger-cloud
        # - name: "DAGGER_CLOUD_TOKEN"
        #   valueFrom:
        #     secretKeyRef:
        #       name: dagger-cloud
        #       key: token
        volumeMounts:
          - mountPath: /run/dagger
            name: dagger-socket-host

The "dagger-dagger-dagger-helm" makes me think of "duck-duck-duck-goose" 🤣 especially after the goose game 🪿

#Tried out the Dagger DaemonSet Helm