AntelopeIO / DUNES

Docker Utilities for Node Execution
Other
26 stars 17 forks source link

'Workspace' is not formally defined in README.md #98

Closed kostia-ivashchenko closed 1 year ago

kostia-ivashchenko commented 1 year ago

Chapter "Concept and operations" in README.md contains the phrase that is started with "The drive/directory that your workspace is in ...". In the meantime it is not defined before what 'workspace' exactly is, whether it is possible to change it, etc. It makes further explanations quite fuzzy, especially for Windows, where disk drives rather than only folder names are involved.

For example, I get the following message:

PS D:\~Blockchain\WAX\DUNE> dune --create-cmake-app hello ./
/host/~Blockchain/WAX/DUNE path not found

Internal Error

And I do not know how to avoid it,

mikelik commented 1 year ago

@kostia-ivashchenko is this issue still happening? I created similar directory structure and it worked properly. Possibly something was fixed already since you raised the issue:

PS C:\~Blockchain\WAX\DUNE> dune --create-cmake-app hello ./
PS C:\~Blockchain\WAX\DUNE> dir

    Directory: C:\~Blockchain\WAX\DUNE

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        23.02.2023     11:04                hello

PS C:\~Blockchain\WAX\DUNE> cd hello
PS C:\~Blockchain\WAX\DUNE\hello> dir

    Directory: C:\~Blockchain\WAX\DUNE\hello

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        23.02.2023     11:04                build
d-----        23.02.2023     11:04                include
d-----        23.02.2023     11:04                ricardian
d-----        23.02.2023     11:04                src
-a----        23.02.2023     11:04            442 CMakeLists.txt
-a----        23.02.2023     11:04            462 README.txt
mikelik commented 1 year ago

Can't reproduce. Please create a new issue if it still happens.

mikelik commented 1 year ago

From @nsjames: issue happens when the DUNE working directory (workspace) is on another drive than C:\ Reopening

stephenpdeos commented 1 year ago

We'll spend a few more cycles on this, but if we cannot resolve we will at least update documentation for Windows to specify only installing on C: supported

mikelik commented 1 year ago

In Dune we are limiting Windows disk drives that can be used to C:/ only. I thought I could extend it to other drives, but it seems the real issue is in Docker Desktop, which does not allow to map other drives than C:/.

Example showing that mapping E:/ drive works incorrectly, because it is empty:

PS C:\Windows\system32> docker --version
Docker version 20.10.22, build 3a2c30b
PS C:\Users\mikel\repo\DUNE> docker run -p 8888:8888 -p 9876:9876 -p 8080:8080 -p 3000:3000 -p 8000:8000 -v E:/:/host/e -d --name=dune_container dune:latest tail -f /dev/null
674d20516bfe765205544364394ac7be5bb2d432d1520b393070390ebd5a0fe8
PS C:\Users\mikel\repo\DUNE> dir E:\

    Directory: E:\

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        06.10.2022     15:12                boot
(...)
-a----        20.10.2022     10:11              0 Recovery.txt

PS C:\Users\mikel\repo\DUNE> ./dune -- ls -la /host/e
total 8
drwxr-xr-x 2 root root 4096 Mar  3 17:01 .
drwxr-xr-x 3 root root 4096 Mar  8 11:03 ..
PS C:\Users\mikel\repo\DUNE>

The same but for C:/ drive works fine. I will add to documentation that we are limited by Docker Desktop to use only C:/ drive.