Hey Paul,

Thanks for your response. Yes one issue is 4D uses vm type *hyperv*. I am
more  interested in AWS and they use *Xen*. What will be really good if we
can ship 4D apps as Docker images for Mac and Windows and users just run
get the latest version of the apps via Docker. Another issue would be where
to keep .4DD file + resources and managing Read and Write areas for users
content and Read only App etc...I am not sure if 4d engineering team have
tried Docker as a platform or thinking about supporting it in future...

The best is to try it myself...I am going to try it.and feedback here.

Balinder


On 2 February 2017 at 09:01, Paul Dennis <[email protected]> wrote:

> Hello Balinder,
>
> I run 4d server in hyperv vm all the time. For me it doesnt seem to make
> sense to use a different hypervisor for windows client. I have been looking
> into the new types of vm guest on windows 2016 which includes docker. From
> what I can gather it's a question of portability rather than performance.
> This is a real issue for me so at the moment I'm going to stick with normal
> windows hyperv vm as guest.
> Cheers
> Paul
>
>
>
> --
> View this message in context: http://4d.1045681.n5.nabble.
> com/Running-4D-into-a-Docker-container-and-shipping-it-
> tp5750090p5750095.html
> Sent from the 4D Tech mailing list archive at Nabble.com.
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to