2024-09-02, 02:15 PM
Unfortunately, that is an unofficial installation method and we can't really provide much support for it. My advice would be to seek help from SynoCommunity directly, since they're the ones that configured and maintain that package.
As for whether to reinstall using docker, that is going to depend on your use case. You can lose everything regardless of installation method if you're not backing up regularly, and there are ways to transfer your installation even without docker when using operating systems such as Windows and Linux; all you would need to do is clone your drive into a new machine. For that I use clonezilla, but there are many other ways you can use if you do research out there.
The benefits that docker brings to the table are isolation through containers while still retaining performance by directly interacting with the system's kernel, easy portability and quick restoration of a service provided something goes wrong by recreating the container which divides important data in volumes that are preserved outside of it. On the other hand, installing a service bare metal (without any virtualization such as virtual machines or docker) has its own set of benefits, particularly with total access to all hardware and the system without going through hoops, no extra consumption of space because there's no bundling redundant dependencies in containers, and essentially no need to learn docker on top of your regular system administration tasks.
Which one is more beneficial is going to depend on what you intend to do. Personally, learning docker for hosting just one service would be overkill IMO, but if you plan to host many additional services, then learning it could be very useful. It helps with streamlining updating and managing many services at once, and that's where it can truly shine. I like installing JF bare metal because my media server only has that service in it, so it doesn't split any performance with anything else, and virtualization isn't really all that important for me in a computer that doesn't host anything that's particularly mission critical. Also, because I backup my OS installation to restorable disk images, I can always redeploy easily as with docker.
As for whether to reinstall using docker, that is going to depend on your use case. You can lose everything regardless of installation method if you're not backing up regularly, and there are ways to transfer your installation even without docker when using operating systems such as Windows and Linux; all you would need to do is clone your drive into a new machine. For that I use clonezilla, but there are many other ways you can use if you do research out there.
The benefits that docker brings to the table are isolation through containers while still retaining performance by directly interacting with the system's kernel, easy portability and quick restoration of a service provided something goes wrong by recreating the container which divides important data in volumes that are preserved outside of it. On the other hand, installing a service bare metal (without any virtualization such as virtual machines or docker) has its own set of benefits, particularly with total access to all hardware and the system without going through hoops, no extra consumption of space because there's no bundling redundant dependencies in containers, and essentially no need to learn docker on top of your regular system administration tasks.
Which one is more beneficial is going to depend on what you intend to do. Personally, learning docker for hosting just one service would be overkill IMO, but if you plan to host many additional services, then learning it could be very useful. It helps with streamlining updating and managing many services at once, and that's where it can truly shine. I like installing JF bare metal because my media server only has that service in it, so it doesn't split any performance with anything else, and virtualization isn't really all that important for me in a computer that doesn't host anything that's particularly mission critical. Also, because I backup my OS installation to restorable disk images, I can always redeploy easily as with docker.
Server specs => OS: Debian 12 | GPU: Arc A380 | CPU: Ryzen 5 5600X | 64GB RAM | 56TB