The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Deploying RM server on Docker: Creating dev_rm-proxy-svc_1 error
Contributor IHello everyone,
Recently when I deploy RM-Server with Docker on my local Desktop, there is an error occurring.
Envirroment:
Windows 10 Enterprise
Docker: latest stable 2.3.0.4 (46911)
Download image: development and testing purposeInstruction according to docs.rapidminer.com/latest/deployment/docker-compose/
Done:
- Setting the variables PUBLIC_URL and SSO_PUBLIC_URL in the .env file
- Mapping the external port in the docker-compose.yml file at the rm-proxy-svc service definition, because the default ones are occupied
- Running docker network create jupyterhub-user-net-default
- Running docker-compose up -d rm-init-svc
Question:
- After the previous step, an error occurs: Creating dev_rm-proxy-svc_1 ... error (Details seen in log file in attachment). What does it about?
- I have the RM Server locally, so I tried to use HTTP for PUBLIC_URL and SSO_PUBLIC_URL variables at first and don’t use ssh. Does it matter for this error?
0
Answers
it is not a RapidMiner specific issue in general, but relates to some security configuration of the docker-compose on a Windows OS. You sould check your docker-compose security settings and enable the used file pathes to be used as docker volumes. Some related topics can be checked here:
https://stackoverflow.com/questions/60754297/docker-compose-failed-to-build-filesharing-has-been-cancelled
Zoltán
Thanks a lot for your answer. I will try it again and update later.