Hello,
How can I best describe it? I’ll give it a try.
I have four hard drives on my rented dedicated server.
Two SSDs with 2TB each and two HDDs with 8TB each. And perhaps important to mention: only one IP!
The first SSD runs the root drive with Ubuntu 24 and is also my boot drive.
On this SSD, I also run AMP and keyhelp, which manages my web hosting. The two don’t interfere with each other, as AMP fortunately doesn’t use web hosting ports.
However, the SSD has 2TB of capacity, but I can only effectively use 100GB of it for my keyhelp web hosting panel because AMP has somehow divided it up. When I create a server in Amp, it starts in the container, and the game is remounted under /var/lib/docker/overlay2/xxx (it’s even shown to me in keyhelp) with 100GB. If I create a second game, the same one as the first, also with 100GB. Theoretically, I could create about 19 games, but then the SSD would be full (100GB uses keyhelp).
Now to my question: Is it possible to return the 2TB to keyhelp (minus the AMP installation) and move the Docker mounts to one of my hard drives? If possible without reinstalling, the web hosting with keyhelp is active and I will be lynched otherwise 
That’s not how either AMP or docker works
What’s the output of df -h?
I first installed AMP on a fresh Ubuntu installation, then keyhelp.
~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 1.2M 6.3G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 98G 30G 63G 33% /
tmpfs 32G 1.3M 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sdd2 2.0G 100M 1.7G 6% /boot
/dev/sdc 1.8T 3.4G 1.7T 1% /home/ssd2
/dev/sdb 7.3T 348K 6.9T 1% /home/hdd1
/dev/sda 7.3T 44K 6.9T 1% /home/hdd2
overlay 98G 30G 63G 33% /var/lib/docker/overlay2/ceb8ba3a514259eaf18ea9f23f794ebdbc40ce01e34281050bc957137145e577/merged
tmphs
~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 7.3T 0 disk /home/hdd2
sdb 8:16 0 7.3T 0 disk /home/hdd1
sdc 8:32 0 1.8T 0 disk /home/ssd2
sdd 8:48 0 1.8T 0 disk
├─sdd1 8:49 0 1M 0 part
├─sdd2 8:50 0 2G 0 part /boot
└─sdd3 8:51 0 1.8T 0 part
└─ubuntu--vg-ubuntu--lv 252:0 0 100G 0 lvm /
You need to google how to extend a LVM root partition xD
I was already at that point too xD I just don’t understand why only 100GB was allocated, even though I specified during Ubuntu installation that it should use the entire SSD.
I’m just afraid that all my data will be lost if I expand the LVM. -.-
EDIT: Where did the Docker container go after the expansion? oO
~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 1.3M 6.3G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 1.8T 30G 1.7T 2% /
tmpfs 32G 1.3M 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sdd2 2.0G 100M 1.7G 6% /boot
/dev/sdc 1.8T 3.4G 1.7T 1% /home/ssd2
/dev/sdb 7.3T 348K 6.9T 1% /home/hdd1
/dev/sda 7.3T 44K 6.9T 1% /home/hdd2
tmpfs 6.3G 16K 6.3G 1% /run/user/1000
tmpfs 6.3G 16K 6.3G 1% /run/user/0
~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 7.3T 0 disk /home/hdd2
sdb 8:16 0 7.3T 0 disk /home/hdd1
sdc 8:32 0 1.8T 0 disk /home/ssd2
sdd 8:48 0 1.8T 0 disk
├─sdd1 8:49 0 1M 0 part
├─sdd2 8:50 0 2G 0 part /boot
└─sdd3 8:51 0 1.8T 0 part
└─ubuntu--vg-ubuntu--lv 252:0 0 1.8T 0 lvm /
Thanks anyway 
Sometimes you can’t see the forest for the trees^^
The Ubuntu default is to allocate only a certain % up to 100GB because you can’t shrink a LVM volume, only expand it. So if the entire disk was allocated to the root lvm, you couldn’t create any other logical volumes later - defeating the purpose of LVM
The Ubuntu installation UI could be clearer on that though
You won’t lose data. Just got to make sure you expand the filesystem as well after extending the partition
I’ve done that. Thanks for your kind help and your kindness
But the question still remains as to whether Docker containers can be moved to another hard drive. I created the following in the AMP panel, but nothing happens (even after reinstalling via the panel).
Paths were created and assigned to users and groups using
sudo chown -R amp:amp /home/hdd2
If you want instances created on another drive, create a mountpoint on your system for AMP on that drive (such as /mnt/amp), ensure it is in /etc/fstab so it is mounted at boot, make sure the mountpoint is owned amp:amp, and then add it as a datastore in AMP
When creating new instances, select that datastore
The docker mountpoints are for different purposes
ahhhhh okay thank you very much 
The mount point already exists (hdd2) so only the entry in /etc/fstab is missing
