gangefors

I've managed to get a fix for the issue merged into the Community Application store so that anyone installing from there should also get a working configuration. See https://github.com/selfhosters/unRAID-CA-templates/pull/287

I've managed to get a fix for the issue merged into the Community Application store so that anyone installing from there should also get a working configuration. See https://github.com/selfhosters/unRAID-CA-templates/pull/287

Thanks. I managed to install the CA plugin and tried to install aircpp from it. It was immediately obvious that it is based on an incorrect template and I now understand why I had gotten PMs about configuration problems. I managed to find the github repo where the template comes from and opened a PR to hopefully get everything sorted out so that ppl can enjoy a fully functioning application on UNRAID. Thanks for pointing me in the right direction. It's not easy when one doesn't use UNRAID to figure these things out.

Now I feel like I just wasted my time 😆 The reason I did it was that I had gotten one too many PMs about issues ppl had setting up the application. And since I don't use UNRAID myself I had no idea what they needed to do. So I launched a trail in a VM and started testing. I had no idea what is in the pipeline and what features are being thrown out. Neither what the CA is. Anyway, the work has been done and I hope someone can get some use out of it.

The latest image doesn't need the default configfiles to be copied before first boot. The entrypoint script takes care of that since a few versions. I have also taken the time today and created a template for AirDC++ WebClient based on the docker image I provide. Check out the user guide (https://github.com/gangefors/docker-airdcpp-webclient/wiki/UNRAID) or add the template directly (https://github.com/gangefors/unraid-docker-templates/tree/main/). Please report any problems in the issue tracker (https://github.com/gangefors/unraid-docker-templates/issues).

I have created a template for AirDC++ WebClient based on the docker image I provide. Check out the user guide (https://github.com/gangefors/docker-airdcpp-webclient/wiki/UNRAID) or add the template directly (https://github.com/gangefors/unraid-docker-templates/tree/main/). Please report any problems in the issue tracker (https://github.com/gangefors/unraid-docker-templates/issues).

I have created a template for AirDC++ WebClient based on the docker image I provide. Check out the user guide (https://github.com/gangefors/docker-airdcpp-webclient/wiki/UNRAID) or add the template directly (https://github.com/gangefors/unraid-docker-templates/tree/main/). Please report any problems in the issue tracker (https://github.com/gangefors/unraid-docker-templates/issues).

Ivegottheskill messaged me about their issue and the problem was not specifying the correct container path for bind mounting the `/.airdcpp` configuration directory. The . (dot) in the directory name was missing in their configuration causing the application to use an unnamed docker volume as the place to store the configuration (as expected). After setting up the correct bind mount AND copying the default config files to the directory the problem was solved.

I'm happy that I could help. Glad that it finally clicked and you got it running.

Yes, you are not understanding my explanation which means that you don't understand the concept of bind mounts in Docker. Think of your host and the container where the application is running as two separate filesystems. In the docker container configuration where it says "Host Path #" you specify the path on your host. Then just under the host path you specify the path it will get inside the container. That path is what the application will see. It's basically a way to symlink a folder on one filesystem to a folder on another filesystem. So, if you still have /mnt/user/my_share pointing to /Share, when in the application browse to /Share and not /mnt. You should see the content of /mnt/users/my_share in the /Share folder. That is how bind mounts work. You specify a path on the host and then where it will end up in the container. If you want to make it really easy, just mount /mnt/user to /mnt/user and everything will show up as it is on your host even in the container. This is the smallest example I can give you to show how it works. gange@midgard:~/tmp$ touch foo.txt gange@midgard:~/tmp$ ll total 0 drwxr-xr-x 1 gange users 14 May 18 23:13 . drwx------ 1 gange users 250 May 18 23:13 .. -rw-r--r-- 1 gange users 0 May 18 23:13 foo.txt gange@midgard:~/tmp$ pwd /var/services/homes/gange/tmp gange@midgard:~/tmp$ docker run -v /var/services/homes/gange/tmp:/foo/bar/baz alpine ls -R /foo /foo: bar /foo/bar: baz /foo/bar/baz: foo.txt Here you can clearly see that my host path `/var/services/homes/gange/tmp` becomes `/foo/bar/baz` in the container. If you still don't understand I cannot help you further.

If you still have everything configured as show in the first picture you posted, then I would expect it to work. /mnt/user/downloads becomes /Downloads in the container/app and /mnt/user/my_share becomes /Share in the container/app. You should not be looking in /mnt from the apps point of view. It's running in the container, not on the host. You can for example just start the container with your host folders mounted to some other folder in the container, with the same structure for example. Then in the Settings of airdcpp you can browse to those folders and choose them as the share and download folder. This might be the easist way to make it work since then you get to choose mounts youself and then just configure the application to what you have chosen as share/download folders. I hope I made myslef understandable. If not, I would suggest that you first become familiar with how bind mounts work in Docker.

Hi. I'm the author of the Docker image you are trying to use. If you haven't found a way forward yet I think the following will help you on your way. Populate your configuration directory (/mnt/user/appdata/airdcpp) with the following content. https://github.com/gangefors/docker-airdcpp-webclient/tree/master/.airdcpp This should solve your issue. This is documented in the README under the Volume section. https://github.com/gangefors/docker-airdcpp-webclient/blob/master/README.md#volumes I will update my README with the output one gets so that others can find it faster in the README.