#Before I go down this π° π³ further is
1 messages Β· Page 1 of 1 (latest)
Maybe a dev can confirm, but it looks like it might be this issue?
hey @merry gorge! yes, mounting sockets inside Dagger is not currently supported since that requires special handling. That PR that you linked is the correct to follow.
Okay thanks, this probably blocks me from switching to Dagger at work. We run all of our tests with docker compose. Consider this an upvote from me if you have such a thing for prioritising! π
Is the best workaround to export the build and run it on the host with docker compose?
Okay so I've tried using dind as well but that won't work either as the container spun up does not run with privileged mode and there's no capability to pass flags. So exporting the built image and then running the tests on the hosts seems to be the only option. Is there an ETA on bringing back support for mounting the docker socket?
I'll defer the ETA to @sand ivy and @light badger since they have a more clear visibility about current priorities
Well as soon as a user is stuck because of it, it automatically becomes high priority π So if it wasnβt high priority before, it is now. Since the βonlyβ thing holding us up is API design (the feature actually exists in the older dagger 0.2), Iβd say we should be able to ship it by next week
Great, thanks! I'd expect the API will be iterated on anyways, so if we need to update our code further down the road that's fine