What is the status of Sugar on Docker for production environments?

Docker is not currently on the roadmap.  You can see our 8.0 supported platforms at http://support.sugarcrm.com/Resources/Supported_Platforms/Sugar_8.0.x_Supported_Platforms/ 

On a related note... Since you said you've been using Docker for development, hopefully you're aware of Enrico Simonetti's Sugar Docker repo:  GitHub - esimonetti/SugarDockerized: Sugar Dockerized (Sugar application not included. Download at www.sugarcrm.com) .  We use it as part of our Professor M's School for Gifted Coders automation, and it works well.  You can learn more about how we leverage the Sugar Docker repo and see our scripts in the School repo:  GitHub - sugarcrm/school: Professor M's School for Gifted Coders 

Hi Lauren Schaefer,

Not even on the roadmap? That is definitely a pity for an enterprise-grade application in 2018  

This would help us fix some of the issues we encounter for instance with different versions of PHP required by different applications in an information system. 

Although we are perfectly conscious of the vast amount of work invovled, we respectfully insist on having that on your backlog with a higher level of priority

Finally, we are indeed well aware of Enrico's work. This is what we are using 

In 2018, as we build new apps and services on top of Sugar, you better believe we are looking at Docker and Kubernetes as we deploy these things in our cloud.

Now for Sugar (which has been around for a while), all we specify in our supported platforms documentation are the software components. The execution environments are left undefined and up to the partner or customer to decide.

For example, we've never claimed support for Azure Cloud though I'm sure people are running Sugar happily there. That said, SugarCRM isn't equipped to helped a customer configure their Azure hosting environment outside of what's defined in our supported platforms (ex. Linux, MySQL, Apache, and Elasticsearch).

The same analogy applies to Docker. Though I recognize there are some unique challenges.

Damien Pochon are there any product limitations or bugs that you run into when running Sugar in Docker today? File bugs or enhancement requests for them.

In 2018, as we build new apps and services on top of Sugar, you better believe we are looking at Docker and Kubernetes as we deploy these things in our cloud.

Now for Sugar (which has been around for a while), all we specify in our supported platforms documentation are the software components. The execution environments are left undefined and up to the partner or customer to decide.

For example, we've never claimed support for Azure Cloud though I'm sure people are running Sugar happily there. That said, SugarCRM isn't equipped to helped a customer configure their Azure hosting environment outside of what's defined in our supported platforms (ex. Linux, MySQL, Apache, and Elasticsearch).

The same analogy applies to Docker. Though I recognize there are some unique challenges.

Damien Pochon are there any product limitations or bugs that you run into when running Sugar in Docker today? File bugs or enhancement requests for them.

Hello Matt,

Thank you for your reassuring comments: it's good to hear that things are moving in the background. 

Regarding the supported platforms documentation, we took the usual risk-based approach: it's not explicitely in the list, so it's must not be explicitely supported. 

And yes we do have the expertise to setup and configure Portainer/Kubernetes/Openshift platforms, but you mentionned the unique challenges that exist in these contexts and that derive from Sugar's software architecture. I would also add the unique opportunities that come with this technology and the "from pet to cattle" approach. 

I take it that we should be patient and wait for a fully supported stack.

In the meantime we'll probably start working on our first simplified production environment on Docker tech. We'll try to share our insights with the community (and enhancements requests on the portal, of course).