depot

[jagged vault]

@runic cypress your wish is my command 🙂

[delicate light]

Huge fan of depot!

[runic cypress]

Our current experience with Depot

Pros:

• The integration between Dagger and Depot works seamlessly. Additionally, Depot supports non-released Dagger engines, such as depot-ubuntu-24.04-4,dagger=0.17.0-llm.9.
• In our use cases, we have seen a 2-3x speedup when using Depot + Dagger compared to vanilla Github Actions + Dagger.
• The support from Depot is excellent.

Cons:

• The Depot Dagger integration is not currently working with Depot projects as far as I understand.

[jagged vault]

Thanks for sharing your experience!

The Depot Dagger integration is not currently working with Depot projects as far as I understand.

Can you share any more info about this please, what is not working here and how do you expect things to work? 🙂

[runic cypress]

Can you share any more info about this please, what is not working here and how do you expect things to work? 🙂
It's not a bug
There are Projects and Dagger panels
And for the moment all dagger runs are in Dagger panel (splitted by repo)

As far as I can see I can not assign dagger runs to some Depot project

[jagged vault]

Thanks for clarifying! Did you already share this feedback with the depot team as well?

[runic cypress]

Not yet
I will ask them about the future plans for Dagger integration 🙂

[outer tree]

Is the expectation that cache volumes get reused (on subsequent actions) when using dagger and depot (in github actions)? Wondering if i just have this set up wrong, or working as expected.

[dense lion]

Yes that's one of the benefits (as far as I know!)

[outer tree]

That was my understanding. I see "github actions cache" called out in the Cache Explorer, which makes sense. Wondering why none of mine are getting picked up.

[fierce pagoda]

Do you have a Depot org ID for us to check? Yes, a dagger engine invoked via a Depot runner has a persistent cache volume that is orchestrated across builds. Separate from the GitHub Actions cache.

[outer tree]

jpllrgb39n -- i fully suspect i did something wrong lol

[fierce pagoda]

It looks like your GHA jobs didn't specify the Dagger label with the Depot GHA label, thus your Dagger things didn't run on remote Dagger Engines which you can see by the lack of projects in your Dagger tab. You can see an example of how to specify your GHA runner label and dagger version in the runs-on here: https://depot.dev/docs/github-actions/reference/dagger#configuration

[outer tree]

Thank you so much

[outer tree]

Has anyone/can Dagger + Depot run on forgejo? given the pricing changes at github

[dense lion]

You can run Dagger on any CI platform that can run containers (so virtually all of them). Once your pipelines run on Dagger they are very easy to port from Github Actions to elsewhere.

[white wing]

I have dagger cloud setup and have generated the token, however in depot I am not finding CI Runners-->Dagger for some reason and need to add the token there, what can be the issue here?

[junior scaffold]

here

[flat stag]

Hey! Wondering if anyone else had this - we had consistent failures of our dagger pipelines after upgrading to v0.19.11 :

16 : ! open /etc/passwd: failed to mount /tmp/buildkit-mount3005151871: [{Type:overlay Source:overlay Target: Options:[workdir=/var/lib/engine/worker/snapshots/snapshots/116/work upperdir=/var/lib/engine/worker/snapshots/snapshots/116/fs lowerdir=/var/lib/engine/worker/snapshots/snapshots/113/fs volatile index=off redirect_dir=off]}]: mount source: "overlay", target: "/tmp/buildkit-mount3005151871", fstype: overlay, flags: 0, data: "workdir=/var/lib/engine/worker/snapshots/snapshots/116/work,upperdir=/var/lib/engine/worker/snapshots/snapshots/116/fs,lowerdir=/var/lib/engine/worker/snapshots/snapshots/113/fs,volatile,index=off,redirect_dir=off", err: invalid argument

After downgrading back v0.19.10 it went away. Also on v0.19.11 it would typically succeed on restart. I'm suspecting it's this change (not toally sure but it deals w/ volatile dirs): https://github.com/dagger/dagger/commit/cc548f72552d5accd2692d381cb5fdbfbcd26792

[solemn slate]

@flat stag are you on depot? what kernel version are you running on? Looks like your overlay driver doesn't support volatile? https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10
Volatile was introduced in 5.10 onwards

[solemn slate]

strange though.. .just checked the code and we effectively verify if volatile is supported in the underlying FS https://github.com/dagger/dagger/blob/24b5f6f33e5a0570578603689c8c8a27ea424abf/engine/server/snapshotter.go?plain=1#L117 🤔

[flat stag]

yeah depot, no idea what they run but i'd be surprised if it's not a 6.x i can ask

[solemn slate]

@flat stag have you checked to see if this happens in v0.20.1 by any chance?