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
Running the notebook works just fine but I can't find the files after saving them. They are probably not saved to disk at all, even though there is not message in the console. Running the notebook with the -w <working directory> flag does not help either. I get a "Serving notebooks from local directory: ..." message on startup but new files are not saved to that directory. Also tried to start the notebook with the flags described in this stackoverflow post but it did not work either. When I create a new file it shows a "Creating new notebook in " message in the terminal but no path is specified.
I am on OS X and running Docker version 18.06.0-ce.
The text was updated successfully, but these errors were encountered:
Hmm, this probably has something to do with the Docker image - installing & running the kernel natively lets me save and open notebooks fine. Thanks for opening; I'll investigate.
I ran into a similar problem, but implementing the solution as per the linked stackoverflow post solved it for me. If @bi0qaw is still running into this problem, it could help to know which docker command they tried to run.
Running the notebook works just fine but I can't find the files after saving them. They are probably not saved to disk at all, even though there is not message in the console. Running the notebook with the
-w <working directory>
flag does not help either. I get a "Serving notebooks from local directory: ..." message on startup but new files are not saved to that directory. Also tried to start the notebook with the flags described in this stackoverflow post but it did not work either. When I create a new file it shows a "Creating new notebook in " message in the terminal but no path is specified.I am on OS X and running Docker version 18.06.0-ce.
The text was updated successfully, but these errors were encountered: