Quick Update (19/12/2025):

Hi Everyone,

I’ll probably open another topic for this in the coming weeks, as it probably deserves it’s own thread for bug reports and feature requests etc (mostly need to convince myself to write it, but also wanted to double check which category such a thread should go under, is tutorials fine?), but I’ve created an ansible role to help with the installation and configuration of fog.

Notably it will help with creating a secureboot valid setup with shim like above. It should implement most of the important functions of the fog installer, and can also automatically perform a lot of the steps in the guide above for you.

I figured I’d drop it here on the forum somewhere in case it’s helpful for others. More detailed usage information will be added to the readme or the new topic. Naturally I’ll link to a new topic here once I get around to making it.

The role is currently hosted on my forgejo instance here: https://forgejo.cwavs.xyz/Cwavs/ansible-role-fog

I’m going around replying to all these old Docker request threads so people can try out my work. Check out my thread here:

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

and provide feedback in the comments.

the actual github repo is here:

https://github.com/88fingerslukee/fog-docker

@youzersef What if your router providing next server is pfsense.

What needs to be changed in pfsense? My current settings are that of fog.

Pfsense : 10.22.24.1 : (controls DHCP, next server, etc)
Fog 10.22.24.5 : (Working flawless)
iVentoy : 10.22.24.13

Everything I try is sending client back to pfsense, and then errors because it’s getting the boot file for fog, when it’s expecting iventoy_loader_16000

Thanks ! Time to get this project wrapped up 🙂

@george1421 Thanks for your help.

I solve the problem with this AutoUnatted.xml

<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<!-- Bypass OOBE -->
<settings pass=“oobeSystem”>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
<NetworkLocation>Other</NetworkLocation>
</OOBE>
</component>
<component name=“Microsoft-Windows-International-Core” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SystemLocale>pt-PT</SystemLocale>
<UILanguage>pt-PT</UILanguage>
<UserLocale>pt-PT</UserLocale>
<InputLocale>0816:00000816</InputLocale>
</component>
</settings>

<!-- Run SetupComplete.cmd via PostOOBE --> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\FirstBoot\PostOobe" /v "00" /t REG_SZ /d "cmd /c C:\Windows\Setup\Scripts\SetupComplete.cmd &amp; exit /b 0" /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings>

</unattend>

The AutoUnatted.xml will call the the script C:\Windows\Setup\Scripts\SetupComplete.cmd

I make the sysprep with AutoUnatted.xml

Thanks @george1421,
I haven’t setup Fog yet so was looking for a step by step guide to getting it installed and configured.

@Alex78 What do we need to do to gain access to the images? When clicking any of the links, I get “Not Found”.

@george1421
for those struggling with permissions with dev folder.
nfs creates a root:root with 775 permissions and fog ftpuser isn’t part of that group

Just use setgid feature on filesystem . it will enable inheritance
first change the owner of the folders and make “users” the group , lets say fog is your ftp user

chown -R fog:users /volume1/images/

#set inheritance to the dev folder

chmod g+s /volume1/images/dev/

now every new file under dev will have the directory group owner

Regards

@george1421 https://docs.fogproject.org/en/latest/compile_ipxe_binaries
Just throwing in the permalink to the doc on this process.

@yannickF You really should state your issues.

If a feature isn’t available for whatever reason, we will tell you, but leaving us in “uh oh” isn’t really a good approach.

What issue are you having?

@renewedharry

I’m sure some of these parameters are not relevant as I don’t really know what I’m doing,

It looks like you are doing very well.

I can add a little context as in the kernel parameter loads the linux kernel. The initrd commands load these image files onto a virtual hard drive created by iPXE so the kernel can locate them. The .img files would actually be mapped as hard drives to the kernel. The kernel would know how to connect to them and use them.

As for the imgargs these are flags for the kernel as it boots. The different flags tell the startup scripts in the kernel how to react dynamically to the external environment. The alternative would be to build the flags into the kernel, but then you would need to recompile the kernel every time you wanted to make a change. Hint: kernel args are the way to go.

I don’t see much room for improvements with this design. You are currently using http to transfer the boot files. Once the kernel starts up then iPXE is out of the picture. I’m going to suspect most of the slowness is because most of the files are the pmodules directory. iPXE should load bzImage, initrd.img, fu.img and m.img very quickly. Where most of your time is probably once bzImage starts to boot. Then you are at the mercy of what Parted Magic does.

I would like to have a link

@Tom-Elliott Tanks a lot, i gonna check the documentation about PXE boot.
Have a nice day.

@Tom-Elliott I will try thanks.

@george1421

Yes, I changed it, exactly as you just mentioned, and it still didn’t work, it worked fine when I added those two lines of code I mentioned earlier.

Anyway, thank you very much for your help and attention.