Another approach to #selfhosting - this time with quite limited list of functions and more wisdom, I hope.
It is going to be on my trusty Thinkpad x220 with 16 GB and 1 TB ssd, with #Debian and contenerised stack of:
- #Wordpress CMS
- #Moodle #LMS
- Nextcloud AIO
So, obviously, I am writing here to tap some #hivemind wistom, specifically
- What is the least painful way to learn #Docker up to the level I need for this deployment?
- What is the best Moodle LMS image available? I did some research and obviously there is no "official" or "aio" image available. I do not believe I am competent enough to pack my own container, so any and all help would be appreciated.
reshared this
Unus Nemo
in reply to 8Petros [cracking the system for a living] • •@8Petros [cracking the system for a living]
I am sure that you would be competent enough if you get Podman For DevOps . Keep in mind that both Docker and Podman use OCI containers (as do all modern container engines) and a container built with podman would work on either engine. Also because podman was developed to be very docker compatible, anything you have already learned to do with docker is still applicable.
I would also suggest that you build a separate container per service, you are running all the services on one machine with no need for Kubernetes (k8s) and will not worry about distributing your services so you could put all the containers in one pod, which is actually a kubernetes term and not podman, a pod is the smallest unit that can be deployed on a kubernete distributed system (th
... show more@8Petros [cracking the system for a living]
I am sure that you would be competent enough if you get Podman For DevOps . Keep in mind that both Docker and Podman use OCI containers (as do all modern container engines) and a container built with podman would work on either engine. Also because podman was developed to be very docker compatible, anything you have already learned to do with docker is still applicable.
I would also suggest that you build a separate container per service, you are running all the services on one machine with no need for Kubernetes (k8s) and will not worry about distributing your services so you could put all the containers in one pod, which is actually a kubernetes term and not podman, a pod is the smallest unit that can be deployed on a kubernete distributed system (though in this case it would not be being deployed by kubernetes, just your container engine), in order use IPC if required. For instance performance between your db (Maria or Postresql) and php-fpm typically do better with socket than tcp/ip. Not to mention that putting them in a pod would simplify starting and stopping the services. Though after you have the services in a container you can play around and see what performs best for you. The biggest reason to use separate containers is because containers are immutable. To make changes to the container you have to rebuild it from the ground up. So it makes sense to keep the build as simple as possible. Putting all the services in one container would be far more complicated and likely create more layers. It would also be much more work to make adjustments. You would definitely do that type of build with
buildahrather than just using a Containerfile (Dockerfile).See if you cannot at least double the RAM in that system, it will help significantly. Especially if you do anything with tmpfs. Your system uses DDR3 and I was able to get 16gb DIMMs for one of my older laptops. Though the price for 16gb v 8gb is insane. I had to pay $80.00 USD a module vs the $16.00 USD for 8gb.