neolink
neolink copied to clipboard
Docker Compose directory error
Describe the bug
root@Neolink:/# docker-compose up Starting e1ba3a1f7135_neolink ... done Attaching to e1ba3a1f7135_neolink e1ba3a1f7135_neolink | [2022-05-19T10:09:55Z INFO neolink] Neolink 0.4.0 (unknown commit) release e1ba3a1f7135_neolink | Error: Failed to read "/etc/neolink.toml" e1ba3a1f7135_neolink | e1ba3a1f7135_neolink | Caused by: e1ba3a1f7135_neolink | Is a directory (os error 21) root@Neolink:/# ^C
Currently getting this error
To Reproduce Steps to reproduce the behavior. Example: Create Neolink docker-compose Start docker-compose
Expected behavior It to work
Versions NVR software: Neolink software: Reolink camera model and firmware:
You need to provide it with a config file mounted in the right place. There's an example config file in the repo.
In the docker-compose file you've set a w rong local file path:
version: "2"
services:
neolink:
image: thirtythreeforty/neolink
container_name: neolink
ports:
- 8554:8554
volumes:
- >>>WRITE HERE THE PATH TO YOUR CONFIGON YOUR LOCAL MACHINE<<<:/etc/neolink.toml
restart: unless-stopped
Still got the same error :(
@NWalledge perhaps you could post your docker compose file for us any messages you get when you run docker-compose up
@NWalledge I guess you map the directory containing the file instead of the link to the file ?
e1ba3a1f7135_neolink | Is a directory (os error 21)
Be sure to have something like that, pointing directly to the file adress, for each side:
- ./neolink.toml:/etc/neolink.toml
I had the same issue. My docker-compose hat the following as a volume:
config.toml:/etc/neolink.toml
After changing it to the full path it worked perfectly.
D:\Library\Dokumente\SmartHome\Reolink\config.toml:/etc/neolink.toml