To support this channel, joining a Udemy course and leaving positive feedback will be helpful for me. www.udemy.com/course/proxmox-virtualization-environment-complete-training/?referralCode=8E7EAFD11C2389F89C11
Thank you for the video, Sir Ali. I think "Protection" is not about totally isolating the container from the operating system, but to prevent accidental deletion/removal of the container or the virtual machine from the proxmox hypervisor
NIce video! I would like to know if its possible to partition a VM for example /docker 30gb, /var/ 16gb, /root 16gb, /boot 1gb, and then create a template. Or I might partition after cloning from a template. Tia!
The network part doesn't work for me. I am unable to reach my Docker container UI on my host computer (MacOS). Host computer MacOS is accessing PVE on local network (192.168.0.200:8006) which in turn is running Ubuntu as you showed but the container UI comes to be non accessible.
To support this channel, joining a Udemy course and leaving positive feedback will be helpful for me. www.udemy.com/course/proxmox-virtualization-environment-complete-training/?referralCode=8E7EAFD11C2389F89C11
This works in general but Proxmox highly recommend to run docker not in an LXC but in a VM.
Yes if you are using it for Production
@@syncbricks are you stupid?!? then why you did not specify this?
Thank you for the video, Sir Ali. I think "Protection" is not about totally isolating the container from the operating system, but to prevent accidental deletion/removal of the container or the virtual machine from the proxmox hypervisor
You are right, there are various reasons of that. However taking regular backups is better than protection option
NIce video! I would like to know if its possible to partition a VM for example /docker 30gb, /var/ 16gb, /root 16gb, /boot 1gb, and then create a template. Or I might partition after cloning from a template. Tia!
Template for any Lxc container which you configured can be created
But for exact scenario I have never tried
The network part doesn't work for me. I am unable to reach my Docker container UI on my host computer (MacOS). Host computer MacOS is accessing PVE on local network (192.168.0.200:8006) which in turn is running Ubuntu as you showed but the container UI comes to be non accessible.
You can’t access docker UI
You need to install portainer as webui