![]() Then I just got the default config out of the image and into my host with a cp -r /nxfilter/conf/* /tmp/conf, stopped the container, deleted the temporary mapping, and added the usual /mnt/user/appdata/nxfilter/conf : /nxfilter/conf. I temporarily mapped /mnt/user/appdata/nxfilter/conf : /tmp/conf, and connected to the container using docker exec -it /bin/bash. My quick hackey solution was just to start the docker with all the port and folder mapings *except* the /nxfilter/conf one. ![]() When you don't map any host folders to the container's /nxfilter/conf then it starts up and uses the configuration files in the image itself. NX Filtration reports strong revenue growth in H1 2021 and further progress on strategic expansion Enschede, the Netherlands, 31 August 2021, 07:30 CET ENSCHEDE, THE NETHERLANDS NX Filtration N.V. Whether it's intended or not, that doesn't seem to work with this docker. In unRAID-land we're used to dockers which will populate their /conf folders with default configuration when they're empty on first startup. The reason that the nxfilter-base docker throws the Java exception seems to be that it's not able to deal with an empty conf folder. I know this is a bit of a zombie thread, but I recently ran into the same thing and thought I'd post here for anyone else who's having trouble with this docker. I would be incredibly grateful for any advice please! "Exception in thread "main" Įxception in thread "Thread-0" The appropraite folders get created in my app data but when the docker tries to start i know get SO I edited the docker container and the resulting command run looked like /usr/local/emhttp/plugins//scripts/docker run -d -name='nxfilter' -net='bond0' -ip='192.168.0.17' -privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -v '/mnt/cache/appdata/nxfilter/conf/':'/nxfilter/conf':'rw' -v '/mnt/cache/appdata/nxfilter/log':'/nxfilter/log':'rw' -v '/mnt/cache/appdata/nxfilter/db/':'/nxfilter/db':'rw' 'packetworks/nxfilter-base:latest'Į1a26f37b99126b3cdaec315597a7096a3e59cf24fdbad48f1835ebd30055916" Sorry to take so long to come back and thanks for the advice.
0 Comments
Leave a Reply. |