-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Breakpoints set but never hit in CLI or VS Code #3350
Comments
Very interesting. It used to be that this setup (running linux/amd64 on M1) would fail loudly: #2910. It seems to have progressed now to the point where it fails silently. |
No I wasn't doing this. Just tested that config and it break things further. I can't reach the HTTP server my app is running. I just get Logs
Versionsdocker desktop v4.19.0 (latest) |
As far as I know what you are trying to do (debugging an amd64 application running inside a container running under arm64) is impossible. It would be interesting, however, to find out what docker changed that made this problem look more subtle. |
@aarzilli It looks like there is a misunderstanding. The The issue does not involve "running an amd64 container on an arm64 host" (#2910). It's running an arm64 container on an arm64 host. So I think the issue here is that @dseravalli tries to debug an amd64 application running inside an arm64 container. This is impossible. I think the fix should be removing
(if the application can run on arm64). @dseravalli Can you have a try? |
I had fixed it by changing |
Thanks for confirming! Then I think this issue is a false alarm and can be closed. |
Closing, thanks @ZekeLu for noticing. |
dlv version
)? 1.20.2go version
)? 1.19Configured Dockerfile, docker-compose, and VSCode launch.json for remote debugging, connect to debugger, set breakpoints, executed code. I also tried using the delve CLI.
Dockerfile
docker-compose.yml
.vscode/launch.json
relevant logs:
The text was updated successfully, but these errors were encountered: