Have created a docker image for app about neolink HOT 16 CLOSED

Nice, thanks! Protip, not sure if you know already: when you're doing a source build, you can use FROM to copy files out of a previous image (so that you don't get all the Rust toolchain or all the build intermediates baked into the final image).

from neolink.

If your Dockerfile is open source and automatically built, I'll link to it in Neolink. Or, if you want to help me adapt it, I'm happy to maintain it myself once you get it working.

from neolink.

Yup can send you the Dockerfile in the morning

It’s based just from the standard Ubuntu image + apt install of gstreamer + req, then just a few scripts.

All open source.

from neolink.

https://github.com/thadius83/docker-neolink/

Only requirement is the source files, and the pre-built to be in the build directory

Working on an alpine image to reduce the size. It's the dependencies of gstreamer that cause the bloat, I suspect I could remove a lot of them manually, but lack of time.

from neolink.

Cool. If they're true dependencies, you can't remove them. That's what "dependency" means. But if they're recommendations, you can avoid installing them with --no-install-recommends.

from neolink.

@thadius83 woult you update your image with the latest Neolink files? It looks like my E1 should be supported now and i would really love to try it with your docker image.

from neolink.

@Riza-Aslan give the new official image a shot

from neolink.

Tried the official image but it didn't work for me. Do I have to start it the same way like the unofficial image or is it different? There are no Information about it on the docker page.

root@Synology:~# docker run -p 9554:8554 -v /volume4/docker/Neolink/neolink.conf:/etc/neolink.conf thirtythreeforty/neolink
[2020-07-06T07:56:04Z INFO  neolink] Neolink 0.3.0 (unknown commit) release
Error: IoError(Os { code: 2, kind: NotFound, message: "No such file or directory" })

from neolink.

from neolink.

I may have goofed up the config filename when I redid it, sorry if so.

from neolink.

It's starting fine now, but I cannot connect to the stream. I've build an image based on ubuntu with thadius83's dockerfile earlier and this was working for my E1 cams, but i've got wifi issues because of this. See my comment here #27

from neolink.

With docker image get this error
[2020-07-07T08:18:44Z INFO neolink] Neolink 0.3.0 (unknown commit) release
Error: IoError(Os { code: 21, kind: Other, message: "Is a directory" })
How can i fix it?

from neolink.

I think you have tried to link your configuration file to a folder. You have to start the container like this:

docker run -p 9554:8554 -v /folder/neolink.conf:/etc/neolink.conf thirtythreeforty/neolink

from neolink.

Here's the sample launch command from the readme. Again, the config file ends in toml not conf:

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

from neolink.

Sorry...forgot to change it to toml before posting.

The official image is still not working for me. It's starting like it should and I can see in the logs that the stream has been startet, but I cannot connect to the stream from VLC or my Synology Surveillance Station. It worked with my own image with neolink version 0.2.0 but not yet with the official one. I've exposed 8554 and both clients take very long before telling me that they couldn't connect. If I try it on a closed port the error comes pretty fast. Do you have any ideas?

from neolink.

@Riza-Aslan #33 fixed the obviously broken Docker image. Try again. Thanks @m1k1o .

from neolink.