Hi Everybody!

I’m posting this here in the hopes that people will test this out and provide feedback. I have used fog for a long time and very much wanted an easier way to deploy it using a docker image. I couldn’t find any that were recent or that satisfied my OCD for implementing everything via environment variables, so I went ahead and spent the last several weeks building one out.

I feel like I’m at the stage where it works well enough that I’d love for people to test.

The whole goal was to create an image that could be pulled and run without having to do any building.

A couple of notes:

• It uses a separate container for the DB, but I haven’t yet tested out the use of an already existing DB. I think it is possible by altering the FOG_DB variables and then adjusting the requirements of the fog-server container in the compose file.
• I haven’t yet fully tested several things which are listed on the README. If I’m missing anything there, let me know

Please post in the issues area in the repo.

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

thanks!
Lucas

@Tom-Elliott said in Fog Trunk Autologging Out Immediately:

I did not update the text because I think it’s simpler to enter values in the form of “720 minutes” vs having users run calculations on their own (no offense anybody).

That said, I was unaware the logout time was being done in seconds and not performing the calculation as it had under the legacy client. (Oversight I suppose, for that i’m sorry).

This has been patched and pushed though. Thanks for letting us know.

I agree wholeheartedly and I can confirm that this is now working as it should on the latest 1.3.0-RC2 version.

thanks!

Not sure if anybody has actually had a chance to look at my docker image yet. I’m throwing my hat in the ring for maintaining an official image, but I’d need some help with it.

Because I’m not affiliated with FOG in any official capacity and I’ve never actually contributed to it in any way before, I completely avoided making any actual changes to the source. I have noticed that there could be a couple of things that could make the docker implementation a little easier though, specifically around the FOG services themselves. I’m not entirely sure they are completely container friendly, but I really need more hands on this to test it out thoroughly.

Also, I used Debian 13 as the base image for this and it ends up being pretty large (2.5GB). It might be possible to shrink this with alpine-linux but I didn’t want to break a bunch of stuff and then have to spend more time chasing those bugs. Anybody that wants to work that angle, please feel free.

@Frode-Woldsund

I created an image. Give it a go and let me know

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

@tchavei2

check out my image! Let me know if it works for you

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

@JJ-Fullmer @ramone

I created an image, check my post here

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

I do believe it’ll be able to utilize an existing DB, but I haven’t tested it yet.

please check my post here

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

Hi Everybody!

I’m posting this here in the hopes that people will test this out and provide feedback. I have used fog for a long time and very much wanted an easier way to deploy it using a docker image. I couldn’t find any that were recent or that satisfied my OCD for implementing everything via environment variables, so I went ahead and spent the last several weeks building one out.

I feel like I’m at the stage where it works well enough that I’d love for people to test.

The whole goal was to create an image that could be pulled and run without having to do any building.

A couple of notes:

• It uses a separate container for the DB, but I haven’t yet tested out the use of an already existing DB. I think it is possible by altering the FOG_DB variables and then adjusting the requirements of the fog-server container in the compose file.
• I haven’t yet fully tested several things which are listed on the README. If I’m missing anything there, let me know

Please post in the issues area in the repo.

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

thanks!
Lucas

Thanks for the reply!

Apache is definitely running. When I go to http://x.x.x.x/fog I get the following message:

This is a storage node, please do not access the web ui here!

I have another website on this server, what URL does the master node look to when determining the storage node info?

I have put the correct mysql connections into the fogsettings file.

Anything else I can look at?

Hey everybody,

I used to have this working but I had to reinstall my storage node instance and I can’t get the main server to see the storage node for some reason. I’m running the latest 1.5.8.28 on both servers. I am able to connect to MySQL from the remote host no problem with the username and password that are entered in .fogsettings. Also, the fogproject user has the proper password as defined in .fogsettings.

I see the following when I go to FOG Configuration:

Main Server FOG Version: 1.5.8.28
Storage Node FOG Version: 503 Service Unavailable

Any idea what this means? I don’t think it’s a mysql issue.

thanks
88

@joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee after double checking, the FOG Client does not force log offs; this means that any other user process can stop the log off. This indicates the problem is likely another program on the computer, that or a GPO policy is blocking it.

Could you try running:
shutdown.exe /l manually on a problematic machine and see what happens?

This command works and logs me out. For some reason it isn’t happening automatically

However, ultimately I would recommend using GPO to handle inactivity log outs. There are some known restrictions with the log out module (https://github.com/fogproject/fog-client#autologout)

Can you tell me how I would do inactivity logouts via GPO? The reason I use Fog for this purpose is because there was never any other way to do this.