🥳

👋

👏

away

hey

as usual.

Maybe in the future my dagger.cloud UI can show me details on what actually got executed when 😇

You reminded me that we should change the examples in the docs to use graphql docs, so I made an issue: https://github.com/dagger/dagger/issues/4198

For the UI something like Gitlab pipeline but even better 🙂

Nice!

Also: for curl 🙂

Oh, didn’t know we had this kind of intellisense, cool.

😮

Super nice!

Btw, dagger version on main branch was broken for me today (dagger listen), to investigate

But so useful 😍

dagger listen*

Heads up to everyone that you need to change the “to” in the chat to “everyone” if you want to chat with everyone in the group. Otherwise, it will just send to us panelist directly :)

dagger run is very handy while developing

Oh that makes me want to try the same thing with gqurl by Hasura, graphql auto-complete right from the CLI

https://github.com/hasura/graphqurl

Oh he’s showing rust??

😍

dagger run sh -c 'gq -H "Authorization: Bearer $DAGGER_SESSION_TOKEN" $DAGGER_SESSION_URL'

Very cool demo Marcos, loved the explanations!

Marcos: is there an example repo for the Rust part?

That's super cool!

Yesss, we want to play with rust too

Strong start 🙂

Title is great

I told him the same thing 😂

You got my attention 🙂

How much did you bribe him 🤣

Marcos: similar question to Solomon’s, is this sort of example in the docs? Looks like not yet, eh?

`dagger run`

🔥

Marcos: Oh! Awesome, thanks! I expected/looked for it in the Dagger CLI section…

I’ll make issue for that

(makes sense to me in the graphql API section)

but can't hurt to reference in both places 👍

Mark speaking hard truths 😅

https://github.com/dagger/dagger/issues/4200

There is also the opposite: Works in the CI, can't reproduce locally.

Yes, I have on open PR in that situation 😅

Actually it’s the opposite. Works locally, not on CI.

Oh Vagrant… those old days 🙂

Not THAT old!

Noo, not vagrant. It always takes minutes to build a VM 😢

Right before I learned about Docker

Yeah, for me it was about 10 years ago!

Criticisim of Docker is not allowed here sorry

So true, playing with containers is not that easy

Lol. The number of flags/args shows your skill level. That’s a level 12 `docker run` right there.

🤣

Docker CLI flags madness is what happens when you try to please developers and sysadmins in the same tool

Strategic use of "Dagger is the best" slide to keep us attentive

Great slide, again

🤣

fix ci!

now, really fix

Mark, how do you invoke your pipelines from the CLI?

I assume go run

oh

You can use mage as a library and invoke with 'go run' (or run the compiled binary of course)

Ah I missed it!! Was it `mage` in that command?

Yup

Got it the second time 🙂

Yes. What’s the `-d` flag?

🔭

Mark: do you have an issue with other teams that are not familiar with Go and may not want to use `mage` ?

```Options:-d <string>directory to read magefiles from (default "." or "magefiles" if exists)```

Nice Márk!

Ah, thanks.

Great demo Márk!

Mark: I have a question above 🙂

To clarify that was a JOKE :-D

Bash away

Buildpacks… my first question when I tried dagger out 🙂

Great demo, great slides. Mark: Interested to have your opinion on Nix / Dagger fit. As you seemed to have run your pipeline from Nix

You did it Harsh! OMG

Thank you all!

Thanks for the presentation Márk!

Mark, that was a nice presentation!

Nix is my general package manager and I use it mostly for my development environment!

👏

You’re using the lifecycle, nice!

wow so simple 🙂

As I said, I generally have a bunch of tools that I use for dev, but not in CI: code formatters, protoc, etc. Nix is great at putting those in my path.

Understood 🙏

Dagger is my go to tool for creating CI pipelines. I run the tests, linters, etc locally to verify that my patch is ready to go.

I didn’t quite catch what feature regression has Harsh on a older version…

In the next engine release it will be back as _EXPERIMENTAL_DAGGER_RUNNER_HOST (though, as the name suggests, in an experimental status)

Harsh can you explain how this works? Did you end up having to modify the pack CLI, or do you bypass it altogether?

🙏🏻

Could use Nix for that as well, but it provides a lower level of isolation compared to Dagger/Containers (even with Nix's reproducability features/focus).

[Q] Harsh can you explain what you need the remote runner feature for?

The fact that CI runs in containers gives me an extra level of confidence that it won't break. If something breaks with nix between environments (which often happens on darwin 😄 ) I can mostly easily fix that, but I don't want to do that in CI, because my debugging capabilities are limited there.

Same Q as Solomon here.

Sorry if I missed any of the questions. 😄 Feel free to ask them again.

[Q] So the fact that the dagger engine is not ephemeral (unlike the CI runner) is important Harsh?

It was me 🙂

so the entire buildpack tooling ecosystem is replaced by one exec in a dagger pipeline??

Crazy. I love this demo :-D

😃

[Q] is there additional work needed to support the "auto-discover" feature of buildpacks?

so many questions 😀

Great demo!

Great demo!

Haha, yes. Entire thing is just an Exec 😄

Thanks for that demo Harsh 😄

🔥

👨🏻‍🚒

Thanks Harsh, super awesome, and continuing to work on supporting the remote runner use case :-)

🪖

🪖

⛑️

🪖

Essentially, I have pretty much the majority features of pack CLI but this one talks to Buildkit rather than Docker.

Yay for logging improvements, looking forward to this 🙂

Makeshift emergency helmet deployed

lol

Jeremy 😄

Andrea, heads up. I am not leaving until my mind is blown away.

Zoom bug!!!

Working fine here

wouuuuaaaaouuu

😶‍🌫️

🤯

LOL this is why Andrea always goes last

helmet blown

hahah, totally smells like charm CLI stuff

mind.blown = true

This is pretty damn cool

This is so awesome!

Ok, ok 🤯 🤯 slow down 🤯

vim keys?

Internal brain case pressure reaching critical …

ship it already 🤯

I was just going to ask about CACHED

[Q] Is this based on the raw buildkit event stream, or do we get a fancy Dagger events API as part of this deal? 😁

You finally decided for the full screen idea :)

I'm curious how you're gonna mix both

🤯 love the naming

… I’m imagining some fun things for Extensions… 🙂

Oh man, I love this!

🤩

Whaaat, a third ?

there is still more?

There's more!

But wait, there’s more

🤣

Wow

🤯

whoooooo

WAIT

oh that's d2

THE GRAPH IS NOT INTERACTIVE?PFFFFFFFFF

d2, nice

😍

WHERE IS THE 3D?

Tanguy ➡️🚪 😂

Nice!

from __future__ import 🤯

I suspect this will become a UI/dagger cloud feature?

Impressed by how fast you found out it is d2 😇

😇

Maybe !

;)

dagger-replay --compare? `gh create issue`

really that's it??

No more ?

🎉

😎

I already type git clone

It’s stayed on Andrea’s laptop to protect people’s mind, an helmet is encouraged for the PR review

🤣

[Q] Is this based on the raw buildkit event stream, or do we get a fancy Dagger events API as part of this deal? 😁

Take my money, where do we sign ?

[Q]: I bet it's charm CLI stuff?

Where do I get that T-Shirt? 😄

Mark, all presenters get one, so I will hook you up 🙂

Sweet!

I remember 🙂

Hope they use generics!

Thanks!

🍿

great presentations everyone!

I have to bounce! Bye!

My slides: https://sagikazarmark.hu/slides/2022-12-15-why-dagger-is-the-best

Bye bye everyone

yeah, great prez'

Thanks everyone

Awesome