Docker share - Archive not writable.
See original GitHub issueHi guys 😄
I’ve been experimenting with using dat
as a docker volumes
replacement. It’s been working quite well 🎉 👍 Only issue I’m having is that restarting the share
service gives me an error: Archive not writable, cannot use share. Please use sync to resume download.
.
A quick example:
/Users/asbjorn/tmp/dat-data
❯ docker run --rm -v (pwd)/html:/html -it registry.taghub:5000/dat-data:0.0.1 share /html
dat v13.8.1
Created new dat in /html/.dat
dat://3a2ec47beee3cb74d354908cb7bfe2168616d07d135c22b297251561ef9fe32d
Sharing dat: (empty archive)
1 connection | Download 0 B/s Upload 0 B/s
Watching for file updates
Exiting the Dat program...
/Users/asbjorn/tmp/dat-data
❯ docker run --rm -v (pwd)/html:/html -it registry.taghub:5000/dat-data:0.0.1 share /html
Archive not writable, cannot use share. Please use sync to resume download.
So, I’m starting the share
- everything looks good, the .dat
folder is created etc. However, restarting with the exact same command gives me the above error. I’m pretty sure it’s some docker permissions thing where the uid
og gid
mismatch or something, but I haven’t been able to pin it down. Giving the folder 777 does not seem to help.
So I’ve been wondering how this dat.writable
get’s determined and if we can find a clue there somewhere. Any ideas?
To Dockerfile is just:
FROM node:8
RUN npm install -g dat
ENTRYPOINT ["dat"]
Thanks 👍
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top GitHub Comments
Ah, excellent! Suspected it was something like this 😛 I managed to work around it by simply mounting
/root/.dat
as a volume 👍Thanks a bunch 🎉
Unfortunately, looks like there isn’t an option and it isn’t quite straightforward to add. Our storage APIs are tightly coupled right now ☹️ . This’ll be a good reason to improve that though!
Opened issue in dat-storage too https://github.com/datproject/dat-storage/issues/6