QuantRocket Jupyter 2.11.0 Restart Loop — start.sh Is 0 Bytes

Technical Help
#1

Fresh Windows Docker Desktop install of QuantRocket 2.11.0.
All services start normally except quantrocket-jupyter-1, which repeatedly exits with code 0 and restarts.
docker logs quantrocket-jupyter-1 is empty.
docker run --rm --entrypoint sh quantrocket/jupyter:2.11.0 -c "wc -c /opt/quantrocket/bin/start.sh" returns 0.
I deleted and re-pulled the image, and Docker Hub still serves digest sha256:7823b2de220e76f005f3bd415e09be00cae0cbfd59f4e19552b1b320bbfad3fa.
Architecture is amd64, OS is linux.
A full docker compose down / up -d restart did not fix it.

#2

Try running

docker logs quantrocket-logspout-1

And look for any jupyter logging there.

The start script shouldn't be 0 bytes. When I pull it onto a fresh AMD instance, I get this:

docker run --rm --entrypoint sh quantrocket/jupyter:2.11.0 -c "wc -c /opt/quantrocket/bin/start.sh"
2295 /opt/quantrocket/bin/start.sh
#3

docker logs quantrocket-logspout-1 shows no Jupyter-related logging.
The only transient error is lookup flightlog on 127.0.0.11:53: no such host, after which logspout reconnects normally.
Jupyter still exits with code 0 and restarts, and /opt/quantrocket/bin/start.sh remains 0 bytes.
Since your fresh AMD pull shows 2295 bytes for the same path, what should I check next to determine why my pulled image has different contents?

#4

Things you could try:

  • remove the image with docker image rm quantrocket/jupyter:2.11.0 then pull it again with docker compose pull jupyter
  • if you're not using Docker for anything else, try completely uninstalling Docker and installing everything fresh.
  • in your docker-compose.yml, change quantrocket/jupyter:2.11.0 to quantrocket/jupyter:2.10.1 then run docker compose up -d to see if the older image runs fine
  • If you have another computer, try installing fresh on that.