but still windows is unable to run a docker binary locally despite the very great strides they are making to make that happen with the WSL
the key is that most docker images are 64-bit linux ELF binaries at their base, which means you have to have a 64-bit linux kernel running somewhere somehow, which is why on mac and win virtualbox is used to run a VM in the background
docker does run on other platforms (most notably the rpi), but the images must be rebased entirely
and to my knowledge no mac or windows solution exists without a virtualized linux kernel somewhere running
and I misstated the above, the docker binary (built by go) does indeed run on windows, the daemon does not which runs containers, ie if you follow this page you can get docker up and running just fine on windows (but the thing that is running your containers is a headless VM running in the background a la vbox).
After toying around with gatsby I think it would be possible to make a commercial whatever you want in gatsby IF you were using reactioncommerce as just a backend graphQL api, but anything in the imports directory is going to share memory with the rest of reaction and therefore be subject to the GPLv3
I'm also of the opinion that this is the reason magento and wordpress in particular are stricken with so many security vulnerabilities. Both Magento and Wordpress core are usually not the issue, in my experience the third party proprietary plugins are the first to go unattended with well known vulnerabilities that stay open for years.
If this means no paid Reaction Commerce plugins ever, that's pretty bad news from a business perspective. One major point for developers and agencies in a CMS/platform is to distribute commercial plugins.
guys I'm trying to deploy a reaction image using docker connected to a mongo server, but whenever I deploy I get the following error like 10 times in a row: WARN Reaction: Error while importing to Packages: Updating the path 'layout' would create a conflict at 'layout'
Maybe it has to do with the fact that I'm running mongo ver 3.6?
and most of the core plugins aren't loaded afterwards, the admin dashboard only has 4 icons instead of the usual
also getting that same error with "icons" and "settings" in place of layout
@rhaix that is interesting to note on 3.6, at one point I was using an ancient mongo default install from debian and ran into some strange issues as well (it wasn't readily apparent it was mongo related). I'm not certain this is detailed anywhere in the docs, but I think 3.4 is definitely the preferred mongo version
@loanlaux@joshuacox Thanks for your questions/answers on this. Just wanted to let you know we're gonna get official answers on this and will update the FAQ with it soon! I'll make sure to ping you when that happens.