![]() Which basically means 'recursively change permissions in /home/jupyter to add write permissions to the group'. In that case you could add your user to the group jupyter editing /etc/group/: jupyter:x:1001:billĪnd then add the appropriate permissions for the group: chmod -R g+w /home/jupyter The first jupyter is the username, the second jupyter is the group name. Take for instance: ls -l /home | grep jupyterĭrwxr-xr-x 13 jupyter jupyter 4096 Sep 8 10:26 jupyter When you run ls -l /home you can see the current permissions of the user folders. If it does work, it still might be a Pi problem, but its more likely that youre accidentally trying to connect to the wrong host. If that doesnt work, then its definitely a problem on the Pi-side. You could have added your username to the jupyter group instead of taking ownership. Easier sanity check: login remotely locally and try to ssh to pilocalhost. Never worked in that same scenario, but I would guess that jupyter is just a typical user with a home folder. So my question is this: how can I change /home owner to my_username but still allow Jupyter to run my notebooks? Is this a setting within Jupyter or do I need to do something else? My goal is to freely transfer files with WinSCP without messing with changing jupyter ownership of the directories. In order to run them, I had to revert ownership back to ‘jupyter’. I am trying to upload a custom remote. But when I attempted to run my notebooks in gce, they would not run. ![]() This allowed me to copy all my local data to gce via WinSCP. I then used $ sudo chown -R my-username ~/jupyter to change ownership to my username. After much frustration, I found this was due to the /home directories being owned by ‘jupyter’. So after creating several datasets locally, I tried to copy the folders to my vm instance using WinSCP. In order to save GCP billing time, I cloned the fastai course v3 and libraries on my local machine which allows me to play with non-compute intensive operations like data set creation, etc. ![]() Login command: $ gcloud compute ssh -L 8080:localhost:8080
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |