Skip to content

Commit d5e9db3

Browse files
committed
Troubleshooting
Signed-off-by: Cédric Foellmi <cedric@onekiloparsec.dev>
1 parent 799d093 commit d5e9db3

2 files changed

Lines changed: 17 additions & 0 deletions

File tree

docs/local/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,3 +18,4 @@ Here is a quick guide to get you started with Arcsecond.local:
1818
4. **Data Management**: Learn how to store and manage your observational data using Arcsecond.local's robust data
1919
management capabilities. [IN PREP]
2020

21+
[Troubleshooting](troubleshooting.md).

docs/local/troubleshooting.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Troubleshooting
2+
3+
## Windows + Docker Desktop: “/data is not writable” troubleshooting blurb (copy/paste)
4+
5+
- Check Docker Desktop is running (the whale icon should be active). If it isn’t, docker compose commands may hang or
6+
fail.
7+
- Verify the host folder exists and is accessible: create the directory referenced by SHARED_DATA_PATH in File
8+
Explorer (and ensure you can create a file in it).
9+
- Avoid network / cloud-synced paths at first (common culprits: UNC paths like \\server\share, mapped drives,
10+
OneDrive/SharePoint-synced folders). Prefer something simple like C:\Users\<name>\ArcsecondData.
11+
- If you use another drive (D:\ / external drive): enable sharing in Docker Desktop. Go to Docker Desktop → Settings →
12+
Resources → File sharing (wording may vary) and add the drive/folder, then Apply & Restart.
13+
- Confirm the mount from inside a container (quick sanity check): Run a one-off container that writes a test file to
14+
/data and confirm the file appears on the host. If it can’t write, it’s almost always a sharing/permissions/path
15+
issue.
16+

0 commit comments

Comments
 (0)