Best posts made by Nil

Nil

Hi guys

This post is the continuation of my request for help that I posted 6 weeks ago on this same forum
Link here

It worked for me, and I tested all the functionality that FOG offers and I did not encounter any problems.

Proxmox 6.3-3
LXC : Debian 10.7
FOG : 1.5.9

So here is how to install FOG (Normal / Storage) in an LXC Container under PROXMOX 6

When creating the LXC Container uncheck the checkbox
Unprivileged container

Otherwise it will be impossible to activate NFS as well as Nesting in the advanced options of the LXC.

Then go to the options tab of the LXC.
LXC > Options > Features> Edit

Check the NFS & Nesting boxes.
(As below) Restart the LXC.

The LXC options :

NFS : of course for the NFS Server…
Nesting : if is not check you will have SQL issues

And next perform a classic installation, and you will have a FOG Server running on a LXC Container

On the wiki there is “way” to install FOG on a LXC but is a little “outdated”. And it is WAY EASIER to check a box in the GUI rather than modify the configuration file of the LXC it self (i think)

Nil

@Sebastian-Roth you were right the problem came from the LXC container.
@george1421 I have run showmount -e 127.0.0.1 and he return me

clnt_create: RPC: Program not registered

Debian firewall was disabled and the firewall checkbox in the proxmox was unchecked.

So I went to see the LXC container, I did a lot of research and I found

LXC Container in proxmox are created in unpriviled (see checkbox)

It is necessary to uncheck this box to be able to activate the NFS
Then in the container options (see screen)

Go to “Features” and Edit, here you can activate NFS in the WebUI (You can also in cmd line but i dont recommand to that).
Check “NFS” for the NFS … and also “Nesting” otherwise you will get a MySQL error like

Setting up and starting MySQL...............................Failed!

(during the installation process) or the MySQL system will not start on an existing installation

If like me you have an existing installation and you dont want to recreate all the ct from the start, in proxmox go to backup and backup your LXC Container, next restore it and be careful to uncheck the checkbox “Unpriviliged container” (see screen)

Now uploading and deploying image works perfectly
English is not my native language, I may have expressed myself poorly, do not hesitate to point it out to me.

Thanks for your help guys.
Have a nice day

Nil

Hi guys

This post is the continuation of my request for help that I posted 6 weeks ago on this same forum
Link here

It worked for me, and I tested all the functionality that FOG offers and I did not encounter any problems.

Proxmox 6.3-3
LXC : Debian 10.7
FOG : 1.5.9

So here is how to install FOG (Normal / Storage) in an LXC Container under PROXMOX 6

When creating the LXC Container uncheck the checkbox
Unprivileged container

Otherwise it will be impossible to activate NFS as well as Nesting in the advanced options of the LXC.

Then go to the options tab of the LXC.
LXC > Options > Features> Edit

Check the NFS & Nesting boxes.
(As below) Restart the LXC.

The LXC options :

NFS : of course for the NFS Server…
Nesting : if is not check you will have SQL issues

And next perform a classic installation, and you will have a FOG Server running on a LXC Container

On the wiki there is “way” to install FOG on a LXC but is a little “outdated”. And it is WAY EASIER to check a box in the GUI rather than modify the configuration file of the LXC it self (i think)

Nil

@george1421

I don’t know if I have a COMPLETE solution (At the moment I’m just cloning and deploying images and it works great)

I haven’t tried all of the functionality Fog offers yet, but I will be doing so very soon.

I am a student in computer science and currently in internship, I have already written a tutorial (in French for my internship) but for me it would be very interesting to help the fog community so I will write one in English for the LXC containers .

The LXC container part in the wiki is outdated (2018), I mean there are a lot easier now. how is it going? I write it and then I send it to you?

Nil

@Sebastian-Roth you were right the problem came from the LXC container.
@george1421 I have run showmount -e 127.0.0.1 and he return me

clnt_create: RPC: Program not registered

Debian firewall was disabled and the firewall checkbox in the proxmox was unchecked.

So I went to see the LXC container, I did a lot of research and I found

LXC Container in proxmox are created in unpriviled (see checkbox)

It is necessary to uncheck this box to be able to activate the NFS
Then in the container options (see screen)

Go to “Features” and Edit, here you can activate NFS in the WebUI (You can also in cmd line but i dont recommand to that).
Check “NFS” for the NFS … and also “Nesting” otherwise you will get a MySQL error like

Setting up and starting MySQL...............................Failed!

(during the installation process) or the MySQL system will not start on an existing installation

If like me you have an existing installation and you dont want to recreate all the ct from the start, in proxmox go to backup and backup your LXC Container, next restore it and be careful to uncheck the checkbox “Unpriviliged container” (see screen)

Now uploading and deploying image works perfectly
English is not my native language, I may have expressed myself poorly, do not hesitate to point it out to me.

Thanks for your help guys.
Have a nice day

Nil

@george1421 Thanks for your answers

Yes I hand edit the exports file, i have seen that fsid=0 and fsid=1 was missing so I added it and retry the upload and it was the same result. Can it come because I edited the exports file ?
I dont have access to my server now, i will have acces Monday so i am gonna try showmount -e 127.0.0.1 but in my memory when i run showmount -e x.x.x.x
that return me a things like that

clnt_create: RPC: Program not registered

And also i will look to the firewall.
And maybe I will try to redo an installation on another LXC container and if it does not work I will do it on a VM…

Nil

Hi,

I run Fog on a debian 10.5 with dhcpmasq in proxmox container.

When i try to upload my image from my host to the server…

alt text

Here is my cat /etc/exports

/images                        *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev                    *(rw,async,no_wdelay,no_root_squash,insecure)

I think the bug is relative to NFS but i cant find what goes wrong…
So when i run service nfs-kernel-server status

* nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset:
   Active: inactive (dead)

Jan 08 12:47:12 fogSIS systemd[1]: Dependency failed for NFS server and services.
Jan 08 12:47:12 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
Jan 08 12:54:51 fogSIS systemd[1]: Dependency failed for NFS server and services.
Jan 08 12:54:51 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
Jan 08 12:55:23 fogSIS systemd[1]: Dependency failed for NFS server and services.
Jan 08 12:55:23 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
Jan 08 12:55:38 fogSIS systemd[1]: Dependency failed for NFS server and services.
Jan 08 12:55:38 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
Jan 08 13:14:29 fogSIS systemd[1]: Dependency failed for NFS server and services.
Jan 08 13:14:29 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start

service nfs-kernel-server restart

A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

journalctl -xe

-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit run-rpc_pipefs.mount has entered the 'failed' state with result 'exit-c
Jan 08 13:16:11 fogSIS systemd[1]: Failed to mount RPC Pipe File System.
-- Subject: A start job for unit run-rpc_pipefs.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit run-rpc_pipefs.mount has finished with a failure.
--
-- The job identifier is 764 and the job result is failed.
Jan 08 13:16:11 fogSIS systemd[1]: Dependency failed for RPC security service for N
-- Subject: A start job for unit rpc-gssd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit rpc-gssd.service has finished with a failure.
--
-- The job identifier is 763 and the job result is dependency.
Jan 08 13:16:11 fogSIS systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start fai
Jan 08 13:16:11 fogSIS systemd[1]: Dependency failed for RPC security service for N
-- Subject: A start job for unit rpc-svcgssd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit rpc-svcgssd.service has finished with a failure.
--
-- The job identifier is 767 and the job result is dependency.
Jan 08 13:16:11 fogSIS systemd[1]: rpc-svcgssd.service: Job rpc-svcgssd.service/sta
Jan 08 13:16:11 fogSIS systemd[1]: nfs-config.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit nfs-config.service has successfully entered the 'dead' state.
Jan 08 13:16:11 fogSIS systemd[1]: Started Preprocess NFS configuration.
-- Subject: A start job for unit nfs-config.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--

thank you in advance

Nil

@Nil

Best posts made by Nil

Latest posts made by Nil