capturing image issue
- 
 Hello everyone, 
 I’ve seen some posts talking about similar issues to mine but none of them helped me, so I’m asking here.
 When I try to capture an image, this happen :
  I tried to upload a Windows 10 and 7 image, and tried with fresh install on Fog 1.5.0 and 1.4.4 : same issue. 
 When I do a ls - la on /images I got this :
  but when I try to mannually mount /images/dev on /images I got this : but when I try to mannually mount /images/dev on /images I got this :
  I did a lot of things that I saw on other posts without success (like modifying nfs parameters, etc…). I did a lot of things that I saw on other posts without success (like modifying nfs parameters, etc…).
 I’m running on Proxmox VE 5.1, and the Vm for the fog service is a debian 8.0. All my network is on 192.168.12.XXX.
 Thanks in advance for your help.
- 
 @charlie Can you post the output of this command: showmount -e 127.0.0.1?
- 
 Thanks for your answer, it gave me this message : 
  
 does it have a relation with the nfs service ? Sorry i’m a beginner with Linux.
- 
 @charlie Yes, this tells us that the nfs service is not running on your fog server, or you did not disable the native linux firewall. 
- 
 @george1421 Thanks again, I tried this 
  
 and then
  
 and I got this
  
 but I’ve still the “Programm not registred” when I do the showmount.
 So, i tried to start the nfs service :
  
 Should I update something or did I missed something when I installed ? Sorry again I’m not familiar with linux.
- 
 @charlie said in capturing image issue: I’m running on Proxmox VE 5.1, and the Vm for the fog service is a debian 8.0. 
 …
 Not starting NFS kernel daemon: no support in current kernel. ... (warning).I’ve had that too back when using FOG in a Proxmox container. First you need to check if the nfsd module is installed and loaded in your Proxmox host system (not the VM but the underlaying system!): # modprobe nfsd # lsmod | grep nfsd nfsd 312315 14 # grep nfsd /proc/filesystems nodev nfsdThen you need to sort of activate that module for the VM as well: # vzctl stop $CONTAINER_ID # vzctl set $CONTAINER_ID --feature nfsd:on --save # vzctl start $CONTAINER_IDNow when the VM is back up you should see a proper output running showmount -e 127.0.0.1…LXC ContainersFor those take a look at the forum post here: https://forums.fogproject.org/topic/7978/fog-in-lxc-container-how-to-configure-nfs-server 
- 
 @sebastian-roth Hello and thanks for your answer. I followed your instructions so I got : 
  
  
 but then I got this :
  
 Do I need to download or update something for this command to be recognized ?
 Thanks in advance.
- 
 @sebastian-roth I also did edit the file /etc/apparmor.d/lxc/lxc-default-cgns as shown in your link. 
- 
 @Charlie What kind of VMs/containers do you use on your Proxmox server? 
- 
 @sebastian-roth I’m using LXC containers. 
- 
 @Charlie Maybe this would help? https://forum.proxmox.com/threads/is-it-possible-to-run-a-nfs-server-within-a-lxc.24403/ 
- 
 @sebastian-roth Thanks again for your help, I’ll try this when I’ll go back to work. I’ll keep you informed about it. 
- 
 hello, 
 I couldn’t find a solution to unlock my situation, I tried many things on promox and on fog, without succes again. So I decided to start a new install on another post, separated from the proxmox and it’s working fine. I think I’ll keep this solution so, thanks for your help and sorry to leave an unsolved issue, see you later !
