I'm running Proxmox v4.2-2. On it i've create some container based on Ubuntu 16.04 template.
Now, I need to customize the template. Add apt packages, customize some files, etc. How could I acheive this with ProxMox. There's some doc but always talking of using OpenVZ.
I've also create a Template from a VM, but also, it does not seemds to be a VZ template and I don't think I can export it.
Any idea how to acheive this?
Thank you.
Full backup the VM and recorvey on all VM if you want.
Related
I'm creating a custom vhd image to make it available in azure market place. Its an inbuild centos 7 machine and I want to load it as an image. Is it mandatory to have WALinuxAgent agent to be installed as part of the image? Here is the documentation which says to install it https://learn.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-centos#centos-70. I want to exclude that package from the image. Is that okay to do that ?
You do need it, otherwise the VM may not boot. This agent communicates with the Azure fabric to provide VM status amongst other things. You can find more information about it here: https://github.com/Azure/WALinuxAgent
Being quite new to Azure, does anyone know how to map a Blob File storage on Linux PHP7.2 box as PAAS ?
I looked at the documentation followed the instruction, but they do not work on my App Service.
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-how-to-mount-container-linux
According to this documentation, Blobfuse needs to be installed in order for this to work.
I cannot install Blobfuse, lsb_release -a does not work (part of the instructions), according to terminal the installed package is linux 4.4.0-128.154.
I can find a Wordpress plugin that uses the Wordpress CLI, but that is not really what I am looking for. (I dont use Wordpress on my site, but I thought the code could give me a hint)
I am just looking for a file share to add store uploaded images.
Has anyone done this before?
Thanks in advance !
We have a VM ARM template which runs a custom extension when we provision it. This extensions run fine and install framework correctly.
By looking at verbose log it seems like it runs the extension every time we run deployment script even if VM is already present. Is this correct?
Also if it does run the extension every time, is there anyway to avoid it?
Basically every time the VM is rebooted or the same template is deployed again, the extension is run but only if the new configuration is different from the old one. It can rerun if the force rerun flag is set.
Hope this helps! :)
I am new to Azure Portal but have good knowledge with VMware ESX and vcenter. I created some vm images in Azure portal (not classic) and need to clone them. However, all online docs point to "Capture" button which for some reason is missing from my profile. I found some docs about using AZcopy tool which is fairly complex.
also, because I have some automation customized in the VM, running sysprep might break the tool/automation. so I prefer without running sysprep.
So the bottom line is that I need a way to clone single VM into multiple VMs without running sysprep. Yes I know about the conflicts and hopping I can do the modifications manually. But even if it is impossible without sysprep, fine. As long as I can clone them I'll live with sysprep somehow.
This is possible using Powershell and sysprep. This blog post has a step by step of how it's done.
http://www.codeisahighway.com/how-to-capture-your-own-custom-virtual-machine-image-under-azure-resource-manager-api/
If the Capture button is missing try to check whether your machine is a "Managed disk" one.
If it's not you can follow this tutorial to turn it on but I guess there's costs associate to it.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/convert-unmanaged-to-managed-disks
ps: last time I checked "unmanaged disks" and I spent like three hours trying to understand why the capture button has gone.
I am trying to set up a development environment with Vagrant. I am using centOS 6. From what I have read about Vagrant, I should set up provisioning scripts to install the packages I need when I run vagrant up. For me, this process takes quite a while. However, it seems like it would be more efficient to install everything one and create a new box. Is there some advantage to provisioning that I'm missing? What is it best for me to do in this case?
You can provision everything and when you want to run vagrant up for the nth time you can do so without provisioning:
vagrant up --no-provision
As to why provisioning? It's mostly so that you can easily take the base box and then change for example one or more items in the list to see the effect.
But it keeps the base clean and reusable.