@88fingerslukee

Well mate, you did a wonderfull job The only thing that afraid me is maintenance. By not using the fog install script, you have to write your own installer, which could be hard to maintain in the future, i think.

But to be clear, this is by far the best/cleanest work i’ve seen since a while (and i’ve seen a lot of them) :). I guess you did spent a lot of time on this. If i had found your work earlier, i would have, for sure, worked on it !

@Tom-Elliott said in FOG Docker image:

@Cpasjuste if you have github you likely have ability to have copilot to help read the repo and help you build the README if you find it lacking.

Just thoughts, but thanks for this.

Hi @Tom-Elliott ! I’m not a big fan of ia but i should take a closer look someday

Hi there !

I’ve been working the last few days on a fog docker image. I think it have reached a point were it could be great for me to get some testing and report (especially with the unfs3 server). The image seems to work fine, but i did only test it in a small home lab, and didn’t try things like snapping, wol, ping host and such. Consider this a work in progress.

I’m very bad at readme and such (boring!) but i did try to write a small one which should help to understand how it work (and the challenge behind this image). It is available on my github.

I can’t wait for your feedback, and i hope you’ll like it ! In the meantime, here is a docker compose sample to get up and running in a few seconds (i hope!):

services:
  fog:
    image: cpasjuste/fog
    restart: unless-stopped
    #privileged: true # for nfs-kernel-server mode
    environment:
      HTTP_ADDRESS: 192.168.0.83 # also used for ftp/tftp/nfs/...
      # you can use a custom http port, but storage "Node Disk Usage"
      # and "Bandwidth" graphs wont display correctly. 
      # this can be fixed with a reverse proxy (or use port 80)
      HTTP_PORT: ${HTTP_PORT:-9445}
      PHP_FPM_PORT: ${PHP_FPM_PORT:-9444} # listen on localhost, no need to open port in firewall
      WEB_PASSWORD: ${WEB_PASSWORD:-password} # web user (fog) password
      MYSQL_PASSWORD: ${MYSQL_PASSWORD:-dockerfogsql} # mysql user (fog) password
      # builtin storage (shell/nfs/ftp/tftp...) password
      # use alphanumeric because it is not handled correctly by fog (php?)
      STORAGE_PASSWORD: ${STORAGE_PASSWORD:-dockerfogstorage}
      USE_UNFS3: true # use userland nfs server (no need for privileged mode)
    volumes:
      - database:/var/lib/mysql
      - /images:/images # on host: sudo mkdir /images && chown -R 1000:1000 /images
      #- /lib/modules:/lib/modules:ro # for nfs-kernel-server mode
    network_mode: host # needed ports: https://github.com/Cpasjuste/docker-fog/blob/main/README.md
    
volumes:
  database:

@Tom-Elliott

Thanks and no problem, we know what we sign for when we use the devel branch I’ll update in a few minutes and let you know.
Edit: i confirm that it’s fixed.

Just a little more information i just found : if i click the “force task to start” button in the “Task Management”, then the deploy task does start. By the way, if you need some testing just send me a mail. I do have a good linux and developement knowledge which may help to debug if needed.

@Tom-Elliott sure, here it is ! So i create a basic task (deploy), then it just loop on the “attempting to check in”. This task did work fine (same machine/image) a few hours ago just before i update to latest git (svn).

Hi,

Just a little message to say that i do have the same problem with SVN 6975 : i have an “attempting to check in” loop when trying to restore an image. It was working fine before i updated (i don’t remember which version i was previously but it was SVN 69xx).

I can confirm that latest svn work fine.

Cool, i’ll test right now. Don’t be sorry as we know what can happend if using svn

Hi, i do have the same problem with svn 2785. I also have this error on installing now :
[CODE] * Configuring Fresh Clam…cp: impossible d’évaluer «…/packages/clamav»: Aucun fichier ou dossier de ce type
chmod: impossible d’accéder à «/opt/fog/clamav»: Aucun fichier ou dossier de ce type
Failed!
[/CODE]

[quote=“Cpasjuste, post: 39741, member: 25902”]Yep i confirm that the deployment is now working, thanks (without re-uploading)[/quote]

Yep i confirm that the deployment is now working, thanks

Sure ! I’m on it, i’ll report tomorw

Edit : i should come more on the forum as i’m on this problem since 3 days now

Hi, i have the same problem. I’m also willing to try the svn version, but how does it will work ? We should still rebuild a new image or should we be able to just update fog server then re-deploy ?

Hi, is there any informations about this problem which occur on two different servers for me ?

Hi,

I can confirm that the second time deployement is always working correctly here.

I do have the same problem. Image (multiple partitions single disk) was done on 1.1. I updated to 1.2 (not sure if it is related) and now I do have this error too. The strange thing is I tried a second time without changing anything but this time it worked. But I did had the problem again this morning, I’ll try to redeploy tomorrow to see if the second deployement is working every times.

Note that the windows 7 image have 2 partition (~100mb boot and large data), only the first one give an error.