Go websocket not working in oathkeeper example

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

The go websocket container called ws in the oathkeeper example fails to build. The logs are saying that the executable in the Dockerfile's entrypoint doesn't exist.

Reproducing the bug

1. Run cd code-examples/oathkeeper
2. Run docker compose up --build
3. Go to http://127.0.0.1:4455 and create an account
4. Go to http://127.0.0.1:8080

Relevant log output

Attaching to oathkeeper-kratos-1, oathkeeper-kratos-migrate-1, oathkeeper-kratos-selfservice-ui-node-1, oathkeeper-mailslurper-1, oathkeeper-oathkeeper-1, oathkeeper-postgres-kratos-1, oathkeeper-ws-1
oathkeeper-ws-1                          | exec /ws: no such file or directory
oathkeeper-mailslurper-1                 | time="2022-11-22T23:44:31Z" level=info msg="Starting MailSlurper Server v1.14.1" who=MailSlurper

Relevant configuration

No response

Version

master

On which operating system are you observing this issue?

Linux

In which environment are you deploying?

Docker Compose

Additional Context

I ran it on WSL but it failed on Docker Desktop for Windows too.

Start in code-examples/oathkeeper by running docker compose up --build and inspect the ws container's Dockerfile entrypoint alongside the build output. Done means the ws container starts without the “exec /ws: no such file or directory” error and the documented Oathkeeper example can be reached at the stated URLs.