Question: Error: IoError(Os { code: 21, kind: Other, message: "No such file or directory" }) in Docker about neolink HOT 14 CLOSED

I placed the modified .toml config in root and used the following command to launch:

docker run -p 8554:8554 --restart=on-failure --volume=$PWD/neolink.toml:/etc/neolink.toml thirtythreeforty/neolink

from neolink.

The docker is trying to read the file neolink.conf and mount it at /etc/neolink.conf. Do you have the file neolink.conf outside of your container ready for mounting?

from neolink.

Googling around for info on the container station I think you may need to use a shared folder with the neolink.conf in and set it up as shown in here. I am not an expert on this though.

from neolink.

If you use container station though is it not being hosted externally? I don't expect this method to be able to connect to your camera on your local LAN

from neolink.

Perhaps I am misunderstanding container station though

from neolink.

Oh I see wiki on QNAP suggests you have a box running on your local LAN ok I think I understand now.

But I think your issues if that you have not got the config setup for mounting, please correct me if this is not the case

from neolink.

The docker is trying to read the file neolink.conf and mount it at /etc/neolink.conf. Do you have the file neolink.conf outside of your container ready for mounting?

Yes I have the modified neolink.conf file that I thought I manually copied to the /etc folder. I understand a bit about linux, but the file structure sometimes gets me.

from neolink.

So you've manually put it inside the container at /etc/neolink.conf?

If that's the case you don't need

-v /neolink.conf:/etc/neolink.conf 

Since this line of code is saying:

Find /neolink.conf outside the container and put it inside the container at /etc/neolink.conf

I think that you were getting errors because it wasn't able to find /neolink.conf outside the container

from neolink.

I guess I didn't put it manually in the container no. Just in the filesystem as I thought it would copy it over with that command. I think I was also getting the.toml and .conf confused with each other. I dont actually have a .conf file anywhere that I have created or modified, only the neolink.toml.

from neolink.

When importing the image into container station these are the defaults based on the imported docker image.

from neolink.

I have also modified it to what is below and get the following in the console when trying to start the container.

from neolink.

I placed my modified neolink.toml config file in the Qnap's file dir /usr/local/bin/neolink (because it looks like the command is looking there for the file to copy over to the container file structure /etc/). Maybe I am just not understanding the file structure properly?

from neolink.

Mind you I'm not a docker expert. I was just reading the manual on the -v switch. Perhaps someone who is an expert can comment.

from neolink.

I think I got it figured out for the most part and the container is actually running now. It was having an issue with -v switch and pulling the config from the right path. Thanks for your help in at least pointing me in the right direction, I appreciate it!

from neolink.