Problem with accessing local filesystem -- Directory couldn't be created (error 2: No such file or directory)

[macias]

Thank you very much for creating docker image for amule. I have (hopefully) basic problem, but I cannot resolve it. I used scenario when I have already "old" amule setup i.e.:

docker run -p 4711:4711 -p 4662:4662 -p 4672:4672/udp \
    -e PUID=[wanted_uid] -e PGID=[wanted_gid] \
    -v ~/.aMule:/home/amule/.aMule -v ~/.aMule/Incoming:/incoming -v ~/.aMule/Temp:/temp tchabaud/amule

Which resulted with error:

2020-09-05 15:47:14: Dropping non-existing shared directory: /home/mist/.aMule/Incoming
2020-09-05 15:47:14: Error: Directory '/home/mist/.aMule/Temp' couldn't be created (error 2: No such file or directory)
!2020-09-05 15:47:14: ERROR: Error accessing directory. Could not create the temp directory at '/home/mist/.aMule/Temp'.

"mist" is my user and the location is correct. Hmm, in my case ".aMule" is in fact a symlink, so I thought maybe this is a problem, so I entered the real directory when launching docker. And I got the same result.

Ok, so I renamed my local .aMule directory, and run docker again. With the same result.

So in total those attempts caused two question:

• how to map my local filesystem, so docker container could see it and work with it
• second, how it is possible that even when I changed the local directories in docker call, it still shows an error against "~/.aMule" (in theory it should not be possible, because container does not know anything about local filesystem), only docker itself knows about it, and I changed the call

For the record my call (wrapped as script) is this:

AMULE_DIR=~/.shared/.aMule
docker run -p 4711:4711 -p 4662:4662 -p 4672:4672/udp -e PUID=$(id -u) -e PGID=$(id -g) -v $AMULE_DIR:/home/amule/.aMule -v $AMULE_DIR/Incoming:/incoming -v $AMULE_DIR/Temp:/temp tchabaud/

amule

[macias]

It took me a while to notice -- the problem lies in the amule script -- it contains hardcoded values for mapping both "temp" and "incoming" directory. It would be much more useful to at least fetch the environment variables, so one could pass his/her custom settings using -e switch in docker.