![]() Besides idiotic synology’s docker UI behavior that selects random local port by default – there were no issues of any kind.Īccess to folders and port forwarding is never an issue – docker does not have any impact on folder permissions Port mapping works fine but you can always run container in docker’s host network (for services that only broadcast in local subnet for example – your Home Assistant could be one of those, I haven’t used it so cannot comment)Īlso Nextcloud was hard to setup in Docker while I had more luck by installing manually directly.įor most of these products there are ready-made containers, you don’t have to create you own. I’m running duplicacy, Crashplan and a bunch of other tools in docker for a very long time now, also on synology units. I had mixed results with Docker on Synology so far ![]() Software is almost never built with synology toolchain and environment and synology’s linux version has severely stripped down user mode environment docker on the other hand lets you run you software in the environment it was designed and built for which improves reliability and compatibility and isolation and as a result is much easier to install, configure and manage ![]() Docker recommendation is not for high availability but simply to contain dependencies. ![]() ![]() Yes, I did not imply separate VM server – NAS provides sufficient performance for these types of tasks. I don’t need enterprise availability level, it’s home storage and backup, so it makes more sense to run everything I could on a single machine that run 24:7 and I choose a NAS because it’s quite economical regarding power consumption versus functionality. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |