FOG on LXC

[gusto]

1. I would like to install FOG on LXC (Proxmox 5.4.13). According to this instructions we need to enable it
   Options --> Feature --> Nestig - ON
   This setting ensures the NFS server functionality inside LXC.
   Do I need also to install NFS on a host (proxmox)?
2. According this, components will be automatically downloaded and installed by the FOG installation script: PHP 5/6/7, MySql 5+, Apache 2+, DHCP (any!), TFTP, FTP, NFS. I already have a DHCP server set to mikrotik. At the bottom of the web site is listed
   This works for FOG too by the way you just have to use "undionly.kpxe" instead of "pxelinux.0"
   That means I have to change pxelinux.0 to undionly.kpxe?
3. I have tentatively installed NFS in LXC (centos 7). Then I wanted to destroy the LXC, but I couldn’t destroy the LXC because filesystem in use.

Can anyone advise me?

[gusto]

@Sebastian-Roth
Yes on proxmox

[Sebastian Roth]

@gusto This is run on your Proxmox server console???

[gusto]

@Sebastian-Roth
In this case I get so many rows

....
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
lsof: no pwd entry for UID 48
....

with UID 27,48, 89 …

very thx

[Sebastian Roth]

@gusto Don’t run the command within the fog-server but on your proxmox host after you have tried to destroy it. Make sure you use the right VM ID. It might not be 111 anymore if you keep destroying and re-creating it.

[gusto]

@Sebastian-Roth
This command gives nothing to output

[root@fog-server ~]# lsof | grep vm-111-disk
[root@fog-server ~]# 

Of course I put this question on the proxmof forum, but I didn’t get the answer (see my first post).

very thx

[Sebastian Roth]

@gusto When you see this error message can you run lsof | grep vm-111-disk and post the output here?

https://itsol.biz/lvm-problem-logical-volume-contains-filesystem-use/

This is not at all a FOG specific question and while we try to help I have to say that there are forums out there knowing a lot more about LXC then we FOG people do. Chance is high you get a better answer in a different forum on this specific question!

[gusto]

@Sebastian-Roth
I’m just doing a test. If something doesn’t work, I want to destroy the LXC, but I can’t destroy it because

TASK ERROR: lvremove 'pve/vm-111-disk-0' error:   Logical volume pve/vm-111-disk-0 contains a filesystem in use.

[Sebastian Roth]

@gusto Can you explain why you keep on wanting to destroy the the container??

[gusto]

@Sebastian-Roth said in FOG on LXC:

@gusto Thanks for clarifying! As I see this post is from Nov 1, 2018 - some time after I have used LXC myself. I don’t have a Proxmox server at hand so I can’t try myself, sorry.

• Do you get any error messages?
• What output do you get when running showmount -e in the FOG LXC container?
• Have you tried mounting the NFS share from another machine?

Hi
So again, I have a problem destroying the LXC
I installed FOG without any problems

yum install git -y
cd ~
mkdir git
cd git
git clone https://github.com/FOGProject/fogproject.git
cd ~/git/fogproject/bin
./installfog.sh

I admit that I can destroy the LXC now.
However, now I want to install linux mint over pxe and do this as instructed.
Then I can’t destroy the LXC and get the output

TASK ERROR: lvremove 'pve/vm-111-disk-0' error:   Logical volume pve/vm-111-disk-0 contains a filesystem in use.

showmount in the LXC show

Export list for fog-server:
/images/dev *
/images     *

[gusto]

@george1421
very thankyou

[george1421]

@gusto https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

[gusto]

@Sebastian-Roth

Now everything is all right. I am currently looking for a tutorial on how to set up FOG so I can install various OS over PXE

[Sebastian Roth]

@gusto So is there anything we can do for you?

[gusto]

@Sebastian-Roth said in FOG on LXC:

@gusto Thanks for clarifying! As I see this post is from Nov 1, 2018 - some time after I have used LXC myself. I don’t have a Proxmox server at hand so I can’t try myself, sorry.

• Do you get any error messages?
• What output do you get when running showmount -e in the FOG LXC container?
• Have you tried mounting the NFS share from another machine?

This happened to me before I installed centos 7 from the template and NFS according to the instructions.
Now that I have installed FOG, I will destroy the LXC without any problems. However, I have a plain FOG installed without any settings.

[Sebastian Roth]

@gusto Thanks for clarifying! As I see this post is from Nov 1, 2018 - some time after I have used LXC myself. I don’t have a Proxmox server at hand so I can’t try myself, sorry.

• Do you get any error messages?
• What output do you get when running showmount -e in the FOG LXC container?
• Have you tried mounting the NFS share from another machine?

[gusto]

@Sebastian-Roth
Re: FOG on LXC
nesting
Look at here, there is a link at proxmox forum topis 10

[Sebastian Roth]

@gusto I am not sure I can follow your questions.

According to this instructions we need to enable it
Options --> Feature --> Nestig - ON

Where did you read about “Nesting”? Can see anything about this in the linked wiki article. Did you follow the instructions mentioned in the wiki about Apparmor?

Do I need also to install NFS on a host (proxmox)?

I have done a LXC installations a couple of years ago but can’t remember this part anymore. If it’s not in the wiki I don’t think it’s needed.

That means I have to change pxelinux.0 to undionly.kpxe?

Yes, use undionly.kpxe for legacy BIOS machines and ipxe.efi for UEFI machines. Also see https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence and my post here: https://forums.fogproject.org/post/130612

I have tentatively installed NFS in LXC (centos 7). Then I wanted to destroy the LXC, but I couldn’t destroy the LXC because filesystem in use.

Not sure how to solve this. Not great but rebooting the whole server should definitely fix it.