hey there! there's no limitations | Dagger | Page 1

weary raptor Jan 5, 2024, 1:57 PM

#

ok, I'll try it out, thank you for the feedback

hot vale Jan 5, 2024, 4:20 PM

#

one thing to note about running dagger in testcontainers (though i don't know a huge about testcontainers)
you will need to make sure that dagger is started with the equivalent of --privileged so that it has the permissions neccessary to actually start and manage containers

drowsy lintel Jan 5, 2024, 4:41 PM

#

@hot vale did you mean devcontainers? or you're talking the testcontainers project effectively?

hot vale Jan 5, 2024, 4:41 PM

#

😱 yup, i'm getting confused

drowsy lintel Jan 5, 2024, 4:41 PM

#

🙌

hot vale Jan 5, 2024, 4:41 PM

#

it's a fridaayyy

#

sorry for the confusion 😛

drowsy lintel Jan 5, 2024, 4:42 PM

#

https://tenor.com/h7D0Wu4G2cq.gif

Tenor

torpid cradle Jan 5, 2024, 5:51 PM

#

Im also curious about this, ive just avoided trying to run dagger in devcontainers for now because I thought I'd have to setup something like dind?

#

also wrt devcontainers I usually try to use (or build off) the official MCR images for them ie like mcr.microsoft.com/devcontainers/go:dev-1.21

drowsy lintel Jan 5, 2024, 5:58 PM

#

You're not required to setup dind for Dagger to work. Having said that, having docker installed in the devcontainer makes everything easier as Dagger will use docker automatically to provision the engine

#

Otherwise, you'll have to start the engine yourself in the devcontainer

#hey there! there's no limitations