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
Currently, Ubuntu users cannot simply docker run following the suggested setup in the main readme.
Common error messages were:
rico@laptop$ sudo docker run -p 8888:8888 -v $(pwd):/home/jovyan/work mtasnim/jupyter-pyspark-duckdb
WARNING: The requested image's platform (linux/arm64) does not match the detected host platform (linux/amd64) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error
and
rico@laptop$ sudo docker run --platform linux/arm64 -p 8888:8888 -v $(pwd):/home/jovyan/work -e JUPYTER_ENABLE_LAB=yes mtasnim/jupyter-pyspark-duckdb
standard_init_linux.go:228: exec user process caused: exec format error
(The errors happen in both cases with or without sudo - using sudo was our "last resort")
To overcome issues we had to run the following in our terminals to install the required underlying virtualization software
rico@laptop$ docker run --rm --privileged multiarch/qemu-user-static:register # Not sure this is necessary
rico@laptop$ sudo apt-get install qemu binfmt-support qemu-user-static
It is weird that we require to install this locally, but we assume that these are some hardware virtualization libraries which cannot be brought in to docker.
After the above steps are taken, the remaining commands of the setup should work out of the box.
Currently, Ubuntu users cannot simply
docker run
following the suggested setup in the main readme.Common error messages were:
and
(The errors happen in both cases with or without
sudo
- usingsudo
was our "last resort")To overcome issues we had to run the following in our terminals to install the required underlying virtualization software
It is weird that we require to install this locally, but we assume that these are some hardware virtualization libraries which cannot be brought in to docker.
After the above steps are taken, the remaining commands of the setup should work out of the box.
Thanks @keerthybalan for finding this!
The text was updated successfully, but these errors were encountered: