Locally retrieved cloud instance not working on Docker

Question

Hi there,

I'm facing an annoying issue after downloading and installing locally our cloud instance (recette-icade).

The instance is running on Sugar Serve 14.2.0, my local stack is based on the latest available on github (github.com/.../master)

sugar 14, PHP 8.3.

I'm only getting the login screen, after login a blue screen with the background, no error message at all ...

The inly thing I'm getting in the console is the following message :

Fullscreen

1
2
3
4
5
6
7
8
9
10
11
12
logger.js:75 FATAL[2024-11-21 16:27:50]: Uncaught ReferenceError: showMarketingContentIframe is not defined at http://localhost/sugar/icade/#Administration on line 1
VM641 :1 Uncaught ReferenceError: showMarketingContentIframe is not defined
at HTMLIFrameElement.onload (VM641 :1:1)
at HTMLDivElement.eval (eval at e.exports (addScript.js:9:8), <anonymous>:2:49826)
at He (eval at e.exports (addScript.js:9:8), <anonymous>:2:48094)
at e.<computed>.append (eval at e.exports (addScript.js:9:8), <anonymous>:2:49727)
at e.<computed>.eval (eval at e.exports (addScript.js:9:8), <anonymous>:2:50819)
at B (eval at e.exports (addScript.js:9:8), <anonymous>:2:32425)
at e.<computed>.html (eval at e.exports (addScript.js:9:8), <anonymous>:2:50497)
at child._renderHtml (view.js:296:26)
at child._render (view.js:367:18)
at child._super (component.js:566:34)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

logger.js:75 FATAL[2024-11-21 16:27:50]: Uncaught ReferenceError: showMarketingContentIframe is not defined at http://localhost/sugar/icade/#Administration on line 1
VM641 :1 Uncaught ReferenceError: showMarketingContentIframe is not defined
at HTMLIFrameElement.onload (VM641 :1:1)
at HTMLDivElement.eval (eval at e.exports (addScript.js:9:8), <anonymous>:2:49826)
at He (eval at e.exports (addScript.js:9:8), <anonymous>:2:48094)
at e.<computed>.append (eval at e.exports (addScript.js:9:8), <anonymous>:2:49727)
at e.<computed>.eval (eval at e.exports (addScript.js:9:8), <anonymous>:2:50819)
at B (eval at e.exports (addScript.js:9:8), <anonymous>:2:32425)
at e.<computed>.html (eval at e.exports (addScript.js:9:8), <anonymous>:2:50497)
at child._renderHtml (view.js:296:26)
at child._render (view.js:367:18)
at child._super (component.js:566:34)

The second error message I'm getting on the call to metadata (http://localhost/sugar/icade/rest/v11_25/metadata?type_filter=currencies%2Cfull_module_list%2Cmodules_info%2Chidden_subpanels%2Cjssource%2Cjssource_public%2Cordered_labels%2Cmodule_tab_map%2Cmodules%2Crelationships%2Cserver_info%2Cconfig%2C_override_values%2Cfilters%2Clogo_url%2Clogo_url_dark%2Ceditable_dropdown_filters&platform=base&module_dependencies=1) is the following :

Fullscreen

1
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 14713473 bytes) in /var/www/html/sugar/icade/include/MetaDataManager/MetaDataCache.php on line 115
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 14713473 bytes) in /var/www/html/sugar/icade/include/MetaDataManager/MetaDataCache.php on line 115

Is it possible to help us please ? We can't go further on our developments, and the current recette-icade instance is broken on several layout issues.

Thanks in advance for your help.

Maybe Frédéric Rinaldi , Francesca Shiekh , Enrico Simonetti , Rafael Fernandes have an idea on that ?

How do you manage the cloud instances on local ? What is your procedure to install locally the cloud instances ?

Best regards,

Enes

Enes Saridogan · Accepted Answer

Hi Enes Saridogan 
 The error you are getting about PHP being out of memory is likely to be causing your blank screen I would think. It looks as if you are using the plain Docker setup with no adjustments and the allocated 128Mb of memory is not enough for Sugar. 
 You will need to adjust the PHP memory in the sugar-web1 container upwards, it needs to be at least 512Mb or even higher - in our Docker setups we use 1Gb of PHP memory to be safe I think. 
 When I set up SugarDockerized locally to run instances (we also use this for development) we tend to use the local build version so we can specify the parameters for each container in the Dockerfile accordingly. You may want to take a look at that route as I find it is easier to control everything that way. 
 I also have another word of warning about running 14.x on Dockerized: the pull of the Web1 machine by default include OpenSSL 3.0 which no longer includes the cipher that Sugar / Blowfish uses for encryption of data. That then manifests itself as the system being unable to encrypt / decrypt data - we noticed this by fact of the System Email Settings password never saving. I have a more detailed explanation of what I found and how I fixed that on this thread so you may want to also look at that if building your own local Dockerized container set: RE: Dont send emails with local version 14.0.0 
 Hopefully this helps, 
 Thanks, 
 JH.

Enes Saridogan · Answer

Hi Enes Saridogan and John Hawkins , 
 
 Thank you for reporting this, I did fix our images as well as the OpenSSL 3.0 issue. 
 please clone SugarDockerized again, I'll work on the tests (failing on workflows) when I get back.

Enes Saridogan · Answer

Hi Enes Saridogan , 
 that's odd, it seems the file is actually corrupted. it might be even using some builder cache and not taking the latest. 
 our github actions workflows use (non-cached) versions to build locally and generate our images, so it is something in your machine.. 
 can you please run the following to wipe out your build cache and re-try: 
 docker builder prune --all

Enes Saridogan · Answer

HI Enes Saridogan , 
 Unfortunately toothpaste uses some injection library that is no longer working with the latest versions of Sugar, so I went ahead and updated the script to use a " simpleRepair.php " script I created that does similar things. 
 please refresh your repo and try again