I know this is an ancient topic, but I wanted to make sure I updated anybody who was interested in a docker image to my new one.

please check my post here

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

@ramone

I got your message on the github repo. In regards to the DHCP issue, I’ve updated the code and it should work now. Please test and follow up in the issue thread. Please note that some of the variables in the .env file have changed so you might want to review that before starting it up.

thanks!!

88

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

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.

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

@Wayne-Workman thanks for pinging me about this. @88fingerslukee I’ll need to reproduce this issue before being able to properly address it; hopefully it should not take long.

I run Avast Business Antivirus on the workstations. Both Windows 7 and Windows 10. It obviously doesn’t affect the Windows 7 machines.

I also have GPOs. How do you want me to give you that information?

Has anybody fixed this yet?

@sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee said in AutoLogOut on Windows 10 - Service seems to hang:

Don’t know about other clients because I only have this one on Windows 10 as a test case.

What I meant was “other machines” or do you only have one single PC?

I have a bunch of Windows 7 machines that work just fine. It seems to be isolated to Windows 10.

@sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

@88fingerslukee Sorry for not getting back to you on this for so long. Somehow we must have overlooked this one.

Do you still have that issue? Is it only with one or a couple of clients or do you have this reproducibly on all your clients happening. I don’t think there is any more log that you could provide. But the questions above would definitely help us.

Yes, still having it. Don’t know about other clients because I only have this one on Windows 10 as a test case.

Awesome thanks.

Is there a more detailed log that I can provide?

Server

• FOG Version: 1.4.1
• OS: CentOS 6.8

Client

• Service Version: 0.11.12
• OS: Windows 10

Description

I’m having an issue with the client not logging me out on Windows 10. The .fog_user log has stalled at the last attempt to logout but there are no error messages. The other log file (fog) is still updating. Here are the last lines of the fog_user log.

`------------------------------------------------------------------------------
----------------------------------AutoLogOut----------------------------------

6/23/2017 8:52 PM Client-Info Client Version: 0.11.12
6/23/2017 8:52 PM Client-Info Client OS: Windows
6/23/2017 8:52 PM Client-Info Server Version: 1.4.1
6/23/2017 8:52 PM Middleware::Response Success
6/23/2017 8:52 PM Bus Emmiting message on channel: Notification
6/23/2017 8:52 PM Power Creating shutdown request
6/23/2017 8:52 PM Power Parameters: /l
------------------------------------------------------------------------------`

If I restart the service, the fog_user log starts logging again until the next time it tries to log out.