Closed whytox closed 2 years ago
@whytox I've experienced something similar when trying to re-create a volume with the same name after deleting its pre-existing content (but not the actual bound folder). You can try the following:
docker rm os161
docker volume rm os161-vol
rm -rf "/Users/vito/Dropbox (Politecnico Di Torino Studenti)/Programmazione di Sistema/OS161/os161-volume"
Hope this helps. If not, you can try to use a directory without spaces in its path as the folder that you bind to the volume. Spaces may be what's causing troubles.
Thank you, it worked!
os161user@37c0c72ddc3a:~$ uname -m
aarch64
os161user@37c0c72ddc3a:~$ ls -la
total 32
drwxr-xr-x 9 os161user os161user 288 Mar 18 12:18 .
drwxr-xr-x 1 root root 4096 Mar 18 10:20 ..
-rw-r--r-- 1 os161user os161user 6148 Mar 18 12:17 .DS_Store
-rw-r--r-- 1 os161user os161user 220 Feb 25 2020 .bash_logout
-rw-r--r-- 1 os161user os161user 3771 Feb 25 2020 .bashrc
-rwxr-xr-x 1 os161user os161user 26 Mar 17 19:01 .gdbinit
-rw-r--r-- 1 os161user os161user 807 Feb 25 2020 .profile
drwxr-xr-x 6 os161user os161user 192 Mar 18 12:19 .vscode-server
drwxr-xr-x 7 os161user os161user 224 Mar 18 12:17 os161
Since I own an M1 mac I have compiled the image by myself.
The problem is that when running such images I don't get the os161 directory in /home/os161user if I use a custom volume.
I think the error is on the volume: the container contains all the files when running without a volume.
Here is the inspect command result for the volume:
And here is the command I use to run the image with the volume:
Thank you.