Synology DSM 7.0

[kittmaster]

It's docker linux version, not native Synology build. But if you have an Synology NAS with ability to run Docker, you may run docker version of Serviio. Installation t's just little bit complicated for intermediate user than just installation of standard Synology package. Just install Docker package, then in docker download soerentsch/serviio image and install it. Then you must set mount path to volume and it's done. Last step - go to http://<ip addres of NAS>:23423 in web browser and go change settings of Serviio itself.

You should put together a YouTube video to show the process from start to finish....I think it comes down to.....once you upgrade Synology, you better have a way forward or else Serviio just won't work....and for people to actually see it running and the method it took to get it there would put people's mind at ease.

It is a high risk for those that need Serviio and are unclear on exactly how to implement it in Docker.

It's docker linux version, not native Synology build. But if you have an Synology NAS with ability to run Docker, you may run docker version of Serviio. Installation t's just little bit complicated for intermediate user than just installation of standard Synology package. Just install Docker package, then in docker download soerentsch/serviio image and install it. Then you must set mount path to volume and it's done. Last step - go to http://<ip addres of NAS>:23423 in web browser and go change settings of Serviio itself.

You should put together a YouTube video to show the process from start to finish....I think it comes down to.....once you upgrade Synology, you better have a way forward or else Serviio just won't work....and for people to actually see it running and the method it took to get it there would put people's mind at ease.

It is a high risk for those that need Serviio and are unclear on exactly how to implement it in Docker.

I agree that a video or detailed step-by-step guide would be great. I would be happy to get away from the Synology DSM version of Serviio and be able to run the more current Linux versions. I may test it out, although I have very minimal experience with Docker.

In response to the last post, I think the risk of updating can be mitigated by not upgrading to Synology DSM 7 until you verify that the Docker instance is working. Once you have Serviio confirmed working in the Docker container, THEN you should be able to upgrade to DSM 7. Please correct me if I am wrong with that assumption. Is there anything else that would need to be done with the container after upgrading from DSM 6 to DSM 7, or would it just work (isn't that the purpose of containers to begin with)?

[kittmaster]

It's docker linux version, not native Synology build. But if you have an Synology NAS with ability to run Docker, you may run docker version of Serviio. Installation t's just little bit complicated for intermediate user than just installation of standard Synology package. Just install Docker package, then in docker download soerentsch/serviio image and install it. Then you must set mount path to volume and it's done. Last step - go to http://<ip addres of NAS>:23423 in web browser and go change settings of Serviio itself.

You should put together a YouTube video to show the process from start to finish....I think it comes down to.....once you upgrade Synology, you better have a way forward or else Serviio just won't work....and for people to actually see it running and the method it took to get it there would put people's mind at ease.

It is a high risk for those that need Serviio and are unclear on exactly how to implement it in Docker.

I agree that a video or detailed step-by-step guide would be great. I would be happy to get away from the Synology DSM version of Serviio and be able to run the more current Linux versions. I may test it out, although I have very minimal experience with Docker.

In response to the last post, I think the risk of updating can be mitigated by not upgrading to Synology DSM 7 until you verify that the Docker instance is working. Once you have Serviio confirmed working in the Docker container, THEN you should be able to upgrade to DSM 7. Please correct me if I am wrong with that assumption. Is there anything else that would need to be done with the container after upgrading from DSM 6 to DSM 7, or would it just work (isn't that the purpose of containers to begin with)?

Well that is the problem, usually upgrades don't affect installed apps....in this case...it breaks serviio directly. I don't know how the ROOT user is dealt with in the Docker environment from DSM6 to DSM7......and mind you, it's a one way trip.....there are hacks to get 7 back to 6.....but what a mess that makes.....and then the risk to any data on the drives that goes with it.

So in my humble opinion, for me personally, this is a non starter and I'll just live with DSM6 until some miracle comes along to resolve the mess Synology has created.

Hi, I'm running Servio 2.2.1 in Docker without any problems. I'm using Soerentsch build:

https://hub.docker.com/r/soerentsch/serviio
https://github.com/soerentsch/docker-serviio
https://githubhot.com/repo/riftbit/dock ... /issues/25

Hey,
i´ve tried this one but cant get it to work properly.

  Code:

date   stream   content
2022-05-08T12:34:04.631574649Z   stdout   An unexpected error occurred. Ending the application. Message: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.. Check serviio.log for more details.
2022-05-08T12:34:04.631538746Z   stdout   ... 2 more
2022-05-08T12:34:04.631505028Z   stdout   at org.serviio.profile.ProfileManager.parseProfilesFromFile(ProfileManager.java:184) ~[serviio.jar:?]
2022-05-08T12:34:04.631468151Z   stdout   at org.serviio.profile.ProfilesDefinitionParser.parseDefinition(ProfilesDefinitionParser.java:148) ~[serviio.jar:?]
2022-05-08T12:34:04.631432676Z   stdout   Caused by: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:34:04.631397625Z   stdout   at org.serviio.MediaServer.main(MediaServer.java:137) [serviio.jar:?]
2022-05-08T12:34:04.631357596Z   stdout   at org.serviio.profile.ProfileManager.loadProfiles(ProfileManager.java:158) ~[serviio.jar:?]
2022-05-08T12:34:04.631314932Z   stdout   at org.serviio.profile.ProfileManager.parseProfilesFromFile(ProfileManager.java:186) ~[serviio.jar:?]
2022-05-08T12:34:04.631196468Z   stdout   java.lang.RuntimeException: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:34:04.630738007Z   stdout   12:34:04.614 [main] ERROR org.serviio.MediaServer - An unexpected error occurred. Ending the application. Message: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:34:02.680485374Z   stdout   tail: no files
2022-05-08T12:34:02.679841984Z   stdout   tail: can't open '/opt/serviio/log/serviio.log': No such file or directory
2022-05-08T12:33:59.560682605Z   stdout   An unexpected error occurred. Ending the application. Message: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.. Check serviio.log for more details.
2022-05-08T12:33:59.560362173Z   stdout   ... 2 more
2022-05-08T12:33:59.560327625Z   stdout   at org.serviio.profile.ProfileManager.parseProfilesFromFile(ProfileManager.java:184) ~[serviio.jar:?]
2022-05-08T12:33:59.560288329Z   stdout   at org.serviio.profile.ProfilesDefinitionParser.parseDefinition(ProfilesDefinitionParser.java:148) ~[serviio.jar:?]
2022-05-08T12:33:59.560252535Z   stdout   Caused by: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:33:59.560208401Z   stdout   at org.serviio.MediaServer.main(MediaServer.java:137) [serviio.jar:?]
2022-05-08T12:33:59.560172933Z   stdout   at org.serviio.profile.ProfileManager.loadProfiles(ProfileManager.java:158) ~[serviio.jar:?]
2022-05-08T12:33:59.560133154Z   stdout   at org.serviio.profile.ProfileManager.parseProfilesFromFile(ProfileManager.java:186) ~[serviio.jar:?]
2022-05-08T12:33:59.560083994Z   stdout   java.lang.RuntimeException: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:33:59.559673865Z   stdout   12:33:59.542 [main] ERROR org.serviio.MediaServer - An unexpected error occurred. Ending the application. Message: org.serviio.profile.ProfilesDefinitionException: Profiles definition is not present.
2022-05-08T12:33:57.630136616Z   stdout   tail: no files
2022-05-08T12:33:57.629562791Z   stdout   tail: can't open '/opt/serviio/log/serviio.log': No such file or directory

Volume Mappings
https://www.directupload.net/file/d/654 ... d3_png.htm

Im using the latest version of serviio docker image.

any suggestions ?

Hi MikeFuLLPower,

please check this Thread: https://github.com/riftbit/docker-serviio/issues/30

the mapped paths are empty (no log file, no config file, etc.).
The easiest way to start with the Serviio-Container is: mapp only the media path and optional the /etc/localtime (if there an issue).
Mapp the ports 1900/udp, 8895/tcp, 23423/tcp and use --net=host.

if you mapp optional the other volumes, use

  Code:

docker cp

to copy files from the docker container to your host paths.

More infos to the docker cli: https://docs.docker.com/engine/reference/commandline/cp/

Kind regards
Soeren

I had a docker version running perfectly in DSM 6, but after upgrading to DSM 7.1 it no longer works, I just cant open the console at myip:23423/console/#/app/welcome

Any help would be most welcome



thanks