-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install virtualmin pro under Ubuntu 22.04 (running in an Azure VM) #914
Comments
A tool I'd never come across before today when searching for a fix to these errors is That's a GUI tool though. Is there a terminal friendly equivalent I wonder? I also tried:
Didn't work for me. |
The end of my
|
I've finally got past that error. The fix for me was:
|
Very interesting! Do you know what it was set to before? |
|
We had login issues with our vmin Ubuntu 22.04 VM so we had to restore it to a backup from before I got vmin to install and it would seem that running that chmod command isn't the only thing that I had to do to fix running the vmin install.sh script under Ubuntu 22.04. The problematic thing is that I had tried all sorts of stuff - editing the apt config files, creating and moving gpg keys etc, and non of it seemed to be working but I must've changed something else too apart from doing that chmod command to fix the installation. I'm back to this error when I try running the vmin pro install.sh script:
|
There are two things I mostly recall doing that I think could've fixed this that the commands are absent in my terminal history file, maybe you guys can give me the exact commands I need? There are a couple of apt-key or gpg commands to fetch keys for your repos. I think I might've adjusted them slightly for Ubuntu 22.04 somehow. Another thing I sorta remember doing was running setup-repos.sh -f Which creates a gpg key in /tmp/developers-key.asc and I think I might've used a gpg dearmor command to copy that into the required dir and/or I might adjusted the key file paths to different keys in the apt config files. Any suggestions are gratefully accepted. We're in big hurry to get this server installed. |
I've got it installing again. The magic sequence of commands was:
Then re-run |
this commit from @iliajie is related Add support for Btrfs quotas |
I don’t think it’s related. |
Ok, i posted this here incase it was as it was posted in this guys thread. I can delete it if you want😃 |
This is exactly how our btrfs fstab quotas issue panned out: Our fstab BEFORE running install.sh:
During the running of the install script, the installer warned us:
Our fstab after running install.sh, which failed to boot so we replaced it with the original:
Apart from that we got no errors from |
Are you guys confident that
Then, I can check quotas are enabled like this:
I got these commands from https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org/index.php/Quota_support.html which says its obsolete but all of those commands still seem to work fine, even if that page is obsolete. I should note now that I've never tried to use btrfs quotas before so I've not tested they actually work yet. It doesn't say anything about enabling quotas via fstab which is what |
I'm a ZFS guy but unfortunately we weren't able to use ZFS for this new vmin server because MS Defender doesn't support scanning ZFS pools. :( |
I recently fixed enabling quotas on Btrfs with this patch virtualmin/Virtualmin-Config@483771c correctly in Virtualmin configuration. However, Virtualmin itself doesn’t support it yet... |
I don't think that will be a big deal. I'll just set users quota as part of my user/domain creation script as I did when using vmin with ZFS but vmin integration would be nice for both. |
Ignore my previous post about how to configure BTRFS quotas, which was too incomplete. I am new to btrfs quotas but this is how I understand they work currently, please correct me if you can. First I enabled quota support on my btrfs /home partition, which initially didn't have any subvolumes configured.
I created a "root" subvol for my /home called @home
After creating /home/@home, I copied everything from
Then rebooted to mount my /home in a subvolume. I can then create new btrfs subvol home dirs by running a command like:
Limits can be applied to subvolumes with a command like:
The quota for a users subvol can be checked by running:
The subvol quota being listed as the last (bottom) value in the Thus, putting those commands together allows us to write a Vmin btrfs subvolume creation and deletion script (
After creating that script, you need to tell Virtualmin to run that script by going to https://forum.virtualmin.com/t/introduction-to-btrfs-subvolume-quotas/129708 |
Couldn’t you just run |
We probably could if we were using btrfs for our root partition but we're not, we're using ext4 which is what Azure Ubuntu defaults to. There is Its a good point that my instructions above are only for those with /home on a separate, btrfs drive or partition so aren't suitable for general use yet but I think its still useful info. There's a lot of overly confusing btrfs docs out there! |
We've had to start over with our virtualmin server but I've not been able to get it the latest vmin pro install.sh script to install any packages under Ubuntu 22.04 running in an Azure VM.
As per the vmin download page instructions, I'm trying to install it using the install.sh I downloaded from https://www.virtualmin.com/account/ when signed in.
Apparently
./install -s
should fix the repos but that gives me errors.I can provide any other logs you require.
Hopefully we won't have to install Ubuntu 20.04 and then upgrade from there, it is out of support in a few months so thats only a temp workaround.
I have tried running
After running the
install.sh -s
but that doesn't help.Is the vmin apt repo signed in a way that is friendly with Ubuntu 22.04 and later? It seems they changed the way apt deals with gpg keys in Ubuntu 22.04, apt-key is deprecated. I have read a number of reports of people who can install vmin under Ubuntu 20.04 and then update it to Ubuntu 22 or Ubuntu 24 but cannot get it to install under 22.04 and I can't help but think its this:
https://sites.google.com/site/installationubuntu/home/ubuntu-22-04/apt-key-is-deprecated
The text was updated successfully, but these errors were encountered: