Hello,

 

At the moment, there is no official procedure for updating the application to the docker. You can find the relevant communication in this article on Creatio Academy.

We recommend deploying to the docker only for test environments.

 

Thank you.

Hi, you have two options for keeping data. First - configure your dev environment with persistent volume. In this case, you need to complete and follow the update procedure. But this is a long way. Alternate options (recommended) - save your development data in your packages. You can use a separate package for it. Deploy a clean new Creatio version and install your functional and test data packages on it.  This procedure provides flex scenarios, for example, a fast recovery development environment, easy deployment of new instances of the current version, and an easy way to try a new version without changing your actual environment. 

thank you!

Hello,



As far as we can not help you with this question because we do not know what Creatio package you are using, this question can be resolved as a case for the Creatio Support Team.



If you having problems with sending an email, you can try to connect with us by calling:



 

USA: +1 617 765 7997

UK: +44 20 3384 0040

Australia: +61 261 452 888

Ukraine: +38 (044) 363-31-33



Alternatively, you can send your question through Customer Portal.



Thank you.

 

Good day,

Unfortunately, Creatio support does not have a ready-to-install compose file nor do we have documented instructions to create one.

I will create a request for our developers to create a detailed guide for this task and add it to our Academy.

Thank you.

Hi Artem,

 Any update regarding the compose file , kindly we try to scale our infra machines

Ali Sami,

We have checked this and it has not been implemented yet, but I will mention your inquiry in the registered idea to increase its priority.

Actually it's very simple to run Creatio in Docker. I've wrote a ~30 lines of Docker compose that runs just fine.

The actual pain is Upgrade. If your DB worked with one App version then just starting it with another App version of Creatio simply fails. That's because you need to run "magic" exe that does downloading, upgrading App and DB. 🤮

ildar,

Hi, can you share the Docker Compose?, please to try?

https://github.com/ildar/docker.configs/tree/master/creatio

ildar,

Thanks :-)

Anybody, please, help!

Hi!

Based on the issue you are experiencing with running Clio Docker on Ubuntu 20.04, it seems to be related to compatibility or configuration problems. To address this, I would recommend following these steps:

1. Make sure you have met the minimum system requirements for running Clio Docker on Ubuntu 20.04. Check the official documentation for any specific prerequisites.

2. Double-check that you have correctly followed the installation steps outlined in the documentation or guide provided by Clio.

3. If the issue persists, I suggest visiting the Clio GitHub repository for more information and possible solutions. You can access the repository at the following link: GitHub Repository. Please search for any existing issues that match your problem or consider opening a new issue to report your specific problem. GitHub representatives and the community can provide further assistance and guidance in troubleshooting the issue.

Remember to provide as much detail as possible when reporting the issue, including any error messages or logs you have encountered. This will help the GitHub community understand and address your problem more effectively.

I hope this helps.

Hello Oliver,



Please contact our support team to get the correct installation files for the local environment. 



Best regards,

Bogdan

Thanks Bogdan,

I just did it

Best regards,

Oliver

JUAN PABLO OSUNA DE LEON,

You can also contact the support team directly and specify your issue so we could fix it.

Hello!

As was already mentioned above, please contact the support team directly.



We will provide you with the correct installation files for the local environment. 

I think I’ve managed to solve this problem. In some applications we need to ensure that the user must be connected to the same server during the whole session. So, to allow this I changed the Load Balance Algorithm to source.

frontend front
     maxconn 10000
     #Using these ports for binding
     bind *:80
     bind *:443
     #Convert cookies to be secure
     rspirep ^(set-cookie:.*)  \1;\ Secure
     default_backend creatio
 
backend creatio
     #set balance type
     balance source       
     server node_1 nodeserver1:80 check weight 2
     server node_2 nodeserver2:80 check weight 1

The problem was solved, but I don't know if this is the correct way to solve it. I would like to hear some feedback. Thank you.

Best Regards,

Pedro Pinheiro

Hi Pedro, 



We generally recommend using round-robin, as it's optimal in most cases, but the "source" algorithm is working as well. 

As for why the log-in issue happened: it's hard to say definitely, but on of the options is if the machinekey is different on different nodes - it won't let you log in. 

Best regards,

Yurii.

Hi Yurii Sokil,

I moved this infrastructure to a Linux server. In this server I have the same two instances but with different ports instead of docker containers. How can I generate this "machinekey”?

The documentation only explains how to generate them on windows servers, through  PowerShell.

Best Regards,

Pedro Pinheiro

Hi Jonathan, 



Judging by the error message, the Global Search service cannot access ElasticSearch server. 

You need to specify the Ip of the server where your ElasticSearch is deployed in env file in the folder [services] 



Best regards,

Yurii.