Ammar Bandukwala

I never understood what you found novel about their approach. Aren't they just bind mounting in the Docker socket?

So if the project is at `/home/ammar/Projects/test` on the host it has the same path in the container... Wouldn't we have to overhaul our user system them? Right now the...

Just bind mounting in the project is easy enough... We had a discussion about privileged by default on Slack. You were of the opinion that it's a bad idea then

Also not sure how that bind mount solution helps... If I'm in the container and trying to bind mount my project, I'll probably be using the project directory within `/home/user/`.

Privileged by default is also good with me, so I suppose we should implement proper dind and see where that gets us.

Docker volume mounts ignore user specification On Sat, Apr 20, 2019 at 5:01 PM Anmol Sethi wrote: > They shouldn't be root user by default, should be the same uid...

It's been my experience that the created intermediate directories are owned by root

Pretty sure emacs has built-in headless model

That error is actually masking another one. @kylecarbs is pushing a fix so the terminal tooltip stays open and you can see what the full error is.

@kylecarbs is there any reason why the `$PATH` would be different than the one on the host?