That ihaskell install --stack line from your question is about running the ihaskell kernel with the command to install itself on your system in a place where Jupyter can find it. If you still want to setup the IHaskell environment manually, here is an example from the ihaskell-notebookDockerfile which shows how to run ihaskell install with stack. Again, I recommend you just use the Docker instructions instead of doing this yourself.
It looks like the docker daemon isnāt running. If youāre using Docker Desktop, start the app, check that the ācontainer whaleā in the lower left corner of the window has a green background and when you hover over it, it says āEngine running.ā
The requested imageās platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
docker: Error response from daemon: driver failed programming external connectivity on endpoint learn-you-a-haskell (b6a7d3f54bfded2a72e2f671b078e5c1aaeb306816cffe11ecd4380b19adc5b1): Bind for 0.0.0.0:8888 failed: port is already allocated.
docker: Error response from daemon: driver failed programming external connectivity on endpoint
Bind for 0.0.0.0:8888 failed: port is already allocated.
I donāt know anything about running Linux amd64 images on MacOS Docker Desktop, but it seems like what youāre doing is working. The Jupyter server in the Docker container tries to listen on port locathost:8888 for a connection from your web browser, but it seems like some other process on your system is already listening on port 8888? So you could change the listening port to 8887 like so
This is the full message from Terminal, after executing those commands:
I notice a Notebook work/02-starting-out.ipynb is not trusted message. Not sure if that is related.
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
[I 2023-06-13 13:50:34.501 ServerApp] jupyterlab | extension was successfully linked.
[W 2023-06-13 13:50:34.534 NotebookApp] 'ip' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-06-13 13:50:34.534 NotebookApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-06-13 13:50:34.535 NotebookApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2023-06-13 13:50:34.596 ServerApp] Writing Jupyter server cookie secret to /home/jovyan/.local/share/jupyter/runtime/jupyter_cookie_secret
[I 2023-06-13 13:50:37.347 ServerApp] nbclassic | extension was successfully linked.
[W 2023-06-13 13:50:37.650 ServerApp] All authentication is disabled. Anyone who can connect to this server will be able to run code.
[I 2023-06-13 13:50:37.689 ServerApp] nbclassic | extension was successfully loaded.
[I 2023-06-13 13:50:37.697 LabApp] JupyterLab extension loaded from /opt/conda/lib/python3.9/site-packages/jupyterlab
[I 2023-06-13 13:50:37.698 LabApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
[I 2023-06-13 13:50:37.724 ServerApp] jupyterlab | extension was successfully loaded.
[I 2023-06-13 13:50:37.728 ServerApp] Serving notebooks from local directory: /home/jovyan
[I 2023-06-13 13:50:37.729 ServerApp] Jupyter Server 1.11.2 is running at:
[I 2023-06-13 13:50:37.729 ServerApp] http://5439bdea5dcb:8888/lab
[I 2023-06-13 13:50:37.729 ServerApp] or http://127.0.0.1:8888/lab
[I 2023-06-13 13:50:37.729 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[I 2023-06-13 13:51:16.701 ServerApp] Writing notebook-signing key to /home/jovyan/.local/share/jupyter/notebook_secret
[W 2023-06-13 13:51:16.735 ServerApp] Notebook work/02-starting-out.ipynb is not trusted
[I 2023-06-13 13:51:22.894 LabApp] Build is up to date
[I 2023-06-13 13:51:27.024 ServerApp] Kernel started: e71ef466-12e6-4447-8d17-6c32d0d5c6e4
You are very closeā¦ all of those warning message are routine warnings about things which donāt matter. When I successfully open notebook work/02-starting-out.ipynb then I see those exact same messages. Clearly your computer is running the software in the container.