Official Docker Container

[LogicEthos]

I’m new to Fog, and it looked like a relatively easy setup. It wasn’t.

Incompatibilities with Ubuntu 16.04. I got it partially working in a 12.04 docker container. I gave the container it’s own IP address on the network. But I keep running into problems.

A docker container, with the latest version ready to run would be great.

[Wayne Workman]

FOG 1.2.0 is not compatible out-of-box with Ubuntu 16.

FOG Release Candidate 1.3.0 is. Instructions are here:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

If you can make a ready to go docker container, please share if you are able.

[LogicEthos]

This post is deleted!

[LogicEthos]

Thanks.

I have made progress. I have FOG 1.3.0 running in a container. It was not easy. The main problem was around mysql, and passwords. I started to document it, but found myself travelling in many circles. I’m not entirely sure how I ended up getting it to work. But I will start again from scratch later.

I can PXE boot, but the clients say:

Cannot find disk on system (getHardDisk)

A compatibility test says:

Network [Pass]
Disk [Fail]

Try using a newer kernel. Fog Configuration -> Kernel Update

If I do that, I get:

Error: Failed to connect to server

FTP is working fine. I checked passwords. Tested, using the wiki guide.
What server is it failing to connect to? FTP logs don’t show anything.

[Wayne Workman]

@LogicEthos You should already be using the latest kernel since you installed days ago. The installer pulls the latest fog kernel from fogproject.org every time it runs.

What boot file are you using for dhcp option 067 ? Try using undionly.kkpxe note the extra k.

[LogicEthos]

@Wayne-Workman working now thanks. I didn’t have a disk drive on my client. I didn’t think is was necessary to register with the host.

I was hoping to run a diskless Linux ISO.

[Tom Elliott]

@LogicEthos Why would a diskless host need to be registered in fog?

While it certain “can” be done, it would need to be done manually. The checking fog is going through in the init’s is to determine if FOG can image the device as this, primarly, is what the init’s are designed for.

[x23piracy]

@LogicEthos said in Official Docker Container:

@Wayne-Workman working now thanks. I didn’t have a disk drive on my client. I didn’t think is was necessary to register with the host.

I was hoping to run a diskless Linux ISO.

Hi, is your fog docker project available for the public? I’ve just started today with docker and i am acutally on reading howto use docker
Idea, can we may work together on a fog docker container?

Regards X23

[x23piracy]

@LogicEthos said in Official Docker Container:

Thanks.

I have made progress. I have FOG 1.3.0 running in a container. It was not easy. The main problem was around mysql, and passwords.

Hi,

how did you manage the MySQL Problems in the Docker container, i am actually trying to setup fog in a docker ubuntu 16 and it seems that i am experiencing the same problems then you:

error log:

[x23piracy]

Hi,

if someone is interested i could set this repo to public and interested guys could contribute

Let me know if someone is interested, the repo is empty yet.

[LogicEthos]

@Tom-Elliott I thought that a diskless client, would register with Fog, so that you could decide which image to send it in the future.

[Tom Elliott]

@LogicEthos Registering the system isn’t the problem, but doing so from the init’s is. The init’s aren’t intended to “BE the OS” they’re designed mostly to do stuff with your system disk (or disks). So with this In mind we have checks that ensure that the system is compatible with FOG so fog can use the system as it is intended. A diskless system isn’t capable of uploading, or receiving an image, and because of this the Inits have little bounds to that system. Manually registering should work fine though.

[LogicEthos]

@x23piracy yes, I had the exact same problem with mysql passwords. How I fixed it? I don’t know exactly. I went round in so many circles, I stopped taking notes. Then it worked.

I kept resetting the mysql password at every step if the way. I didn’t use a blank password. Hope that helps.

I was hoping to get to the stage, where I could script the whole build process, and then make that public.