09-27-2020, 06:19 AM
@fitkoh
Yesterday, when I read your OP, I confess that I had at least 3 objections by the time I finished reading it. The most obvious (ie running Docker on an OVZ VPS) has been addressed in my previous post. But there are 2 others that I've left out because they relate to the use of Docker itself inside a VPS! Thus, it's more of a 'philosophical' thing than anything else.
I've been using Docker since it gained traction in 2015/16 and I've developed a practical sense of when it should be used from when it should not (mostly because it's more of a waste of resources, because of the overhead.)
When you deploy your services via Docker on your VPS you consume more resources than it's necessary for those same services to be deployed natively/directly on your VPS, and that only make sense if you're just experimenting with Docker and are willing to incur that penalty OR if you already stack your services as a set of docker images that you migrate from place to place for deployment, of course at the price of that said penalty.
It's for this latter reason -portability- why Docker make more sense in the Cloud environment than in a VPS; and this is why most PaaS (Platform-as-a-Service) make use of them via various Orchestration mechanisms.
The second objection is the use of a control panel for Docker!! but this is personal and has to do with my bigger objection to Control Panels (CP) in general.
You can control Docker via a very limited set of shell commands with the added benefit of pinpointing to the immediate source of error when something goes wrong (and it does very often when you're just setting things up.)
Anyway, I just wanted to be thorough as far as the OP is concerned :-)
Feel free to post any further Docker-related issue, it might make material to interact with, when I visit this forum during the week-ends.
Good luck!
Yesterday, when I read your OP, I confess that I had at least 3 objections by the time I finished reading it. The most obvious (ie running Docker on an OVZ VPS) has been addressed in my previous post. But there are 2 others that I've left out because they relate to the use of Docker itself inside a VPS! Thus, it's more of a 'philosophical' thing than anything else.
I've been using Docker since it gained traction in 2015/16 and I've developed a practical sense of when it should be used from when it should not (mostly because it's more of a waste of resources, because of the overhead.)
When you deploy your services via Docker on your VPS you consume more resources than it's necessary for those same services to be deployed natively/directly on your VPS, and that only make sense if you're just experimenting with Docker and are willing to incur that penalty OR if you already stack your services as a set of docker images that you migrate from place to place for deployment, of course at the price of that said penalty.
It's for this latter reason -portability- why Docker make more sense in the Cloud environment than in a VPS; and this is why most PaaS (Platform-as-a-Service) make use of them via various Orchestration mechanisms.
The second objection is the use of a control panel for Docker!! but this is personal and has to do with my bigger objection to Control Panels (CP) in general.
(09-25-2020, 11:46 PM)fitkoh Wrote: I've been using wordops as a control panel for docker, and usually it works great. Just like I was afraid though, as soon as I try to create my first site, docker starts throwing errors.
You can control Docker via a very limited set of shell commands with the added benefit of pinpointing to the immediate source of error when something goes wrong (and it does very often when you're just setting things up.)
Anyway, I just wanted to be thorough as far as the OP is concerned :-)
Feel free to post any further Docker-related issue, it might make material to interact with, when I visit this forum during the week-ends.
Good luck!