On Sat, Aug 9, 2025 at 6:37 AM 'David Harvey' via sage-support <[email protected]> wrote: > > I could not install sage on debian 13 trixie via apt, so I tried the > docker image instead. > > It was working fine a few days ago, both command line and notebook > versions. > > Today I am having problems with the notebook. > > My command is: > > sudo docker run \ > --rm --interactive --tty \ > --publish 8888:8888 \ > --volume "$(pwd)":/home/sage/host \ > sagemath/sagemath:latest \ > sage-jupyter > > When I run this, I get the following error message, over and over > again, a few seconds apart: > > =============================== > > [W 2025-08-09 11:31:23.714 ServerApp] wrote error: 'Forbidden' > Traceback (most recent call last): > File "/home/sage/sage/local/var/lib/sage/venv- > python3.12.5/lib/python3.12/site-packages/tornado/web.py", line 1788, > in _execute > result = method(*self.path_args, **self.path_kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/home/sage/sage/local/var/lib/sage/venv- > python3.12.5/lib/python3.12/site-packages/tornado/web.py", line 3289, > in wrapper > url = self.get_login_url() > ^^^^^^^^^^^^^^^^^^^^ > File "/home/sage/sage/local/var/lib/sage/venv- > python3.12.5/lib/python3.12/site- > packages/jupyter_server/base/handlers.py", line 753, in get_login_url > raise web.HTTPError(403) > tornado.web.HTTPError: HTTP 403: Forbidden > [W 2025-08-09 11:31:23.717 ServerApp] 403 GET > /api/contents/host/elliptic-recurrences.ipynb/checkpoints?1754739083705 > (@172.17.0.1) 3.68ms > referer=http://127.0.0.1:8888/notebooks/host/elliptic-recurrences.ipynb > > =============================== > > It looks like it's trying to read the notebook elliptic- > recurrences.ipynb, which I was working on a few days ago. But my > understanding is that this should not be possible, because I am > starting up a new instance of the docker image, in a new container (I > checked the old one no longer exists via "docker container list -- > all"). It should have completely forgotten about that notebook. It's > not even accessible in the current directory (which as you can see I > have mapped into the container via the --volume flag), because I am > starting it up in a different unrelated directory. > > So what is going on? How can this instance "see" something from my > previous session? Is it somehow storing something on my actual > filesystem?
A *normal* way to run jupyter in such a scenario would be on the host, with it talking to the remote/guest/container. (If it's the case it would explain what's going on). I would be surprised if you ran it on a browser from the container, this seems to be suboptimal. (but I don't know much about docker) Dima > > thanks > > david > > Confidential communication - This email and any files transmitted with it are > confidential and are intended solely for the addressee. If you are not the > intended recipient, please be advised that you have received this email in > error and that any use, dissemination, forwarding, printing, or copying of > this email and any file attachments is strictly prohibited. If you have > received this email in error, please notify me immediately by return email > and destroy this email. > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/sage-support/63cab78009f62a4f45722d76b2cfa734e4a5142e.camel%40unsw.edu.au. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-support/CAAWYfq134aROovmDO4ad3iPQ0n84WDqzC3Bf6KoJz%3D9umt62zg%40mail.gmail.com.
