Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More details on how to activate the Docker image #9

Open
aaszodi opened this issue Jan 19, 2022 · 1 comment
Open

More details on how to activate the Docker image #9

aaszodi opened this issue Jan 19, 2022 · 1 comment

Comments

@aaszodi
Copy link

aaszodi commented Jan 19, 2022

The current README.md file states that

The commands above do not include activation/licensing configuration; see the official Wolfram Engine Docker image for information on activating the Wolfram Engine kernel.

The problem is that when running the WolframWebEngineForPython (WEPy for short) Docker container, the Python server code is started which invokes the Wolfram kernel and then immediately crashes as there's no license yet. The activation of the Wolfram Engine's Docker image is easy because that image launches WolframScript, but for the WEPy container a workaround is needed:

docker run -it --entrypoint=/bin/bash wolframresearch/wolframwebengineforpython

The --entrypoint /bin/bash overrides the Python server code and launches a shell instead "inside" the container. From that shell one can invoke wolframscript and then it's possible to activate by following the instructions for the Wolfram Engine Docker image. Perhaps it's also possible to invoke WolframScript directly by typing --entrypoint wolframscript but I haven't tried that.

I'd like to suggest that the README.md be updated with this extra information.

@msollami-sf
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants