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

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

I reverted back to a snapshot I had on the same version and it’s working as expected. Unsure how things got corrupted but I would say it’s safe to assume this is working unless others report the same issue.

@chevengur there is not enough information to help you in that picture. If we could see more of the error message that partclone threw (i.e. just above the top of your picture) we would know what happened. At the point in the script all we know is that partclone wasn’t happy.

@JasonNaughton This is a strange one. The linux kernel just doesn’t just invent mac addresses. It would be interesting to look up the first 6 characters of the mac address to see if you could identify the manufacturer.

So are you saying there are 4 physical nics in this computer. LOM, PCie 1, PCie 2? Does that mac address belong to the LOM?

I can say that we are dealing with 2 kernels here. The iPXE boot loader, and FOS Linux. Its technically possible to get to the fog ipxe menu and then when you start up FOS it doesn’t get an IP address because either the nic order has changed or there is missing firmware that is needed to init certain nics.

@Tom-Elliott thx👍

@Clebboii https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

Please see if this helps? Specifically the task related items. Sometimes stale (old/bad items suddenly show up from long ago.) admittedly I’d love to know what caused (or causes?) this but it has so far eluded me this far.

@FlorianLenz I did all these steps and it worked with normal USB adapters, but with USB-C-Ethernet adapters does not work, could you help me out?
(It could be important to know this type-c adapter have 1 HDMI port and 3 normal usb ports)

@Tom-Elliott What’s the difference between the full and quick registration processes then? because AD join exists in full, but not in quick…

@jacaman Does this happen with every HP computer or just one in specific? Does this happen with any other brand/model of computer? Have you tried deploying that same image to another computer? Have you tried replacing any component of the HP computer: HDD/SSD/NVMe, RAM, network adapter (dongle instead of embedded port)?

@sloeckle You can use an older kernel for now, but I’ll work on a fix for this issue. I don’t have access to the hardware needed to reproduce this issue. Are you willing to help us test some kernels?

@Tom-Elliott Cheers, works as expected now!

To add to this, we’ve been imaging a variety of desktop and laptops to Windows 11 last week and we’ve had three occasions where FOG has imaged to a connected portable hard drive rather than the local hard drive. I don’t remember it doing this before.

My technicians are on the lookout and are trying to remember to disconnect portable drives ongoing before a deploy but has something in Windows changed recently? We’re on FOG Version 1.6.0-beta.2233

Thank you!

Ok, nevermind, did the git thing, got it working, cheers 🙂

@Tom-Elliott can confirm, this does now appear to work in 1.6 - huzzah! @george1421 looks like your hard work has paid off and it will eventually be in the stable branch!