You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command ./run_docker --pre-built is mentioned in our docs 12, but actually, it is not working as expected.
The pyodide build artifacts inside the pre-built docker image are in /src/pyodide, but when we do ./run_docker --pre-built, the host file system is mounted to /src, overriding the file system inside the container. So ./run_docker --pre-built works almost just same as ./run_docker.
For now, I think the correct way to use the pre-built docker image is like this:
mkdir dist
docker pull pyodide/pyodide:0.20.0
docker run --it -v $(pwd)/dist:/src/pyodide/build pyodide/pyodide:0.20.0 /bin/bash
$ cd /src/pyodide
$ # Do something inside the docker image...
$ make &&exit# built artifacts are saved to ./dist
So I would like to discuss two things:
We have to either remove --pre-built flag, or fix it to work as expected.
If we decide to remove --pre-built flag, should we still build pre-built docker image? or should we stop providing the image and tell users to usepyodide build instead?
I would be +1 to stop distributing the pre-built image altogether (the deployment CI was broken for the last few releases anyway) in favor of either out-of-tree build or using the pyodide-env image in CI with caching (we should maybe specifically mention how we use ccache).
The command
./run_docker --pre-built
is mentioned in our docs 1 2, but actually, it is not working as expected.The pyodide build artifacts inside the pre-built docker image are in
/src/pyodide
, but when we do./run_docker --pre-built
, the host file system is mounted to/src
, overriding the file system inside the container. So./run_docker --pre-built
works almost just same as./run_docker
.For now, I think the correct way to use the pre-built docker image is like this:
So I would like to discuss two things:
We have to either remove
--pre-built
flag, or fix it to work as expected.If we decide to remove
--pre-built
flag, should we still build pre-built docker image? or should we stop providing the image and tell users to usepyodide build
instead?Related issues:
./run_docker --pre-built
setup #2705WDYT?
The text was updated successfully, but these errors were encountered: