Hi there.
I’m playing around with (go) IPFS for several purposes and I hit a use case that might be bugged.
Basically the use case looks like:
Given:
- A linux/AMD machine.
- An IPFS node with filestore enabled.
- Such node is running inside docker.
- IPFS_PATH is mounted as a regular docker volume mapped to host fs. Also tested the case where no volume is mapped to host fs. So either way.
When:
curl -v -X POST "http://127.0.0.1:5001/api/v0/add?nocopy=true" -F 'file=@${FILE};headers="Abspath: ${IPFS_PATH}/${FILE}"'
Then:
- The file is not at the expected location.
- The response is a normal CID.
- The % of disk usage doesn’t get affected in proportion to added file size. (few kbs change vs couple of Mbs for the file). This hints the file is not “uploaded” or saved somehow.
- The
ipfs filestore lsreports a big list of parts? of the given ${FILE}
Extra details:
- A simple add with nocopy=false works normally.
- I’ve tried to find and read as many issues about this “nocopy” topic as possible, but I couldn’t find any that implies docker. I haven’t (yet) checked if this use case would work out of docker.