Description
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.