René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"More details on how to activate the Docker image","articleBody":"The current `README.md` file states that\r\n\r\n\u003e The commands above do not include activation/licensing configuration; see the official Wolfram Engine Docker image for information on activating the Wolfram Engine kernel.\r\n\r\nThe 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:\r\n\r\n`docker run -it --entrypoint=/bin/bash wolframresearch/wolframwebengineforpython`\r\n\r\nThe `--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.\r\n\r\nI'd like to suggest that the `README.md` be updated with this extra information.","author":{"url":"https://github.com/aaszodi","@type":"Person","name":"aaszodi"},"datePublished":"2022-01-19T20:03:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/9/WolframWebEngineForPython/issues/9"}