hi,
I build an image using endeca-11.3.0-start-services so that when I run this docker image the resulting container will start endeca services and deploy the default discover app. Whenever I run this image the config files in the container location /home/endeca/endeca/apps/Discover/config/script, within the repositoryUrl value, the container id is initialized as shown below instead of http://localhost:8006/ifcr. due to this whenever I access localhost:8006/ifcr the workbench application is not accessible and the page is keep spinning with message [00:48:53] Workbench is starting up (113 of 113 bundles activated, 141 of 190 components ready)... and not proceeding further. Could you please look into this?
for example with in the file WorkbenchConfig.xml
hi,
I build an image using endeca-11.3.0-start-services so that when I run this docker image the resulting container will start endeca services and deploy the default discover app. Whenever I run this image the config files in the container location /home/endeca/endeca/apps/Discover/config/script, within the repositoryUrl value, the container id is initialized as shown below instead of http://localhost:8006/ifcr. due to this whenever I access localhost:8006/ifcr the workbench application is not accessible and the page is keep spinning with message [00:48:53] Workbench is starting up (113 of 113 bundles activated, 141 of 190 components ready)... and not proceeding further. Could you please look into this?
for example with in the file WorkbenchConfig.xml