`make` in docker container `pyodide/pyodide-env` fails with `could not create work tree dir 'emsdk'` about pyodide HOT 8 CLOSED

Thanks

for some reason when you cloned the repo it was owned by a different user and maybe you're in a group that has write permissions or something.

That could be the case, as I cloned the repo with "PyCharm > File > Project from Version Control...".

I had to check if it works without --root if I clone the repo via terminal.

But I would still like to keep the --root note in the docs, as it is nice to know this options exist...

from pyodide.

Agreed. I guess I'll close this then.

from pyodide.

Maybe try ./run_docker --root?

from pyodide.

@hoodmane Thanks, that worked, but the docs don't state that I need root: https://pyodide.org/en/stable/development/building-from-sources.html

from pyodide.

Added a PR for --root option in the docs.

from pyodide.

@hoodmane If I should not use --root what permissions should I set before executing ./run_docker?

from pyodide.

there is something specific to the way permissions are working on your machine that is breaking it without it.

It's a "normal" Ubuntu, no custom changes regarding permissions made actually...

I think it is more likely that, when you (or someone else) checked it on Linux, that you changed some permission once, and forgot about them writing the documentation.

from pyodide.

Well I develop primarily on linux (Ubuntu 22.04.3) and I think most of the main contributors use linux as well. Though I stopped using the docker container a while ago. I think linux is actually the only OS that is at least vaguely well supported. Windows works via WSL and Mac development sometimes is more broken and other times less broken.

When you run run_docker without root, it tries to set up a user inside the container that matches the user outside of the container. If the checkout is owned by your user, this should mean the in-container user has the permission to write to emsdk. My best guesses are:

1. for some reason when you cloned the repo it was owned by a different user and maybe you're in a group that has write permissions or something. but that group info isn't copied into the container for some reason or
2. the run_docker script's code to copy your user into the docker image somehow screwed up and so it sees the inside-docker user as distinct from the outside-docker user and lacks permission.

This is the relevant part of the script:
https://github.com/pyodide/pyodide/blob/main/run_docker?plain=1#L118-L128

from pyodide.