From the Github Repo Readme: These scripts enable users to build a Linux container or virtual machine in an interactive manner, offering options for both basic and advanced configurations. The basic setup utilizes default settings, whereas the advanced setup empowers users to alter these default settings. Through the use of the whiptail command, options are presented to users in a dialog box format. After the user makes their selections, the script collects and verifies the user’s input in order to generate the final configuration for the container or virtual machine.
You must log in or register to comment.
I use these religiously…
However it should be noted… Always check scripts before you run them from the internet.
Having said that… I mirror the whole repo I use it so damn much.And don’t blindly execute stuff from the Internet: https://0x46.net/thoughts/2019/04/27/piping-curl-to-shell/
In this case it’s on github, so the server should be trustworthy, and you can inspect the script before running it. But generally it’s a bad idea.
Great tip to setup a mirror!
I just migrated over from OpenMediaVault to Proxmox VE and it’s a game changer for me. I was running Home Assistant in a KVM instance in OMV, and Docker images on the host OS for well over a year but it kept locking up. I wanted to start fresh, so I went to Proxmox the other day and have been well impressed so far. I ran into those scripts almost immediately and it got me started off on the right foot. So, now I have TWO VM’s one for Home Assistant and one for my Docker instance. Then to replace the NAS, setup my NFS shares on the host which works well.
I wish i found this a month ago.
I discovered it after installing a lot of my LXC containers, too. What I did was test the script and see if it made a better container than I did. If so, I just deleted the other LXC container. I also used it as a way to quickly change the LXC and VM IDs so that they would match the last octet of my internal IP address.
And don’t forget that you can run the Proxmox settings and cleanup scripts at any time.
running scripts like these make me nervous, especially on the host machine of a hypervisor. My (limited) understanding is that a compromised host system compromises all the VMs and containers within. Seems like you could be one command away from letting an attacker into everything.
Yeah personally I’m not a fan and I would rather follow a well-written guide than spend even more time auditing such a script (which would be even more difficult if you’re not experienced with Proxmox). For maintenance’s sake it’s also risky getting your service set up like this as you don’t know how the script set things up and it’s harder to fix things if they go wrong.
