-
Notifications
You must be signed in to change notification settings - Fork 2
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
Golang container doesn't seem to build now #1
Comments
Tanks for identifying the issue @dboreham. Since you have investigated the issue, would you like to PR a fix? I will take a look at it over the weekend otherwise. Thanks again. |
My golang-fu is weak, but sure I'll take a look. |
So...I'm on the verge of random flailing here, but I found what appears to be the current MS go dev container here : https://github.com/microsoft/vscode-remote-try-go/blob/master/.devcontainer/Dockerfile , and when I replace the existing Dockerfile with that one, it seems to work in that I can build and debug pong.go in it. If this sounds reasonable I will make a PR. |
You are heading in the right direction. As you must have seen that the Dockerfiles in the project are created by VS Code and are not written by me. This is the repo used by VS Code to scaffold GoLang dev containers: https://github.com/microsoft/vscode-dev-containers/tree/master/containers/go/.devcontainer I would recommend that you update your remote development extension and then use VS Code to generate devcontainer Dockerfiles for a simple GoLang project. You can then update the Dockerfile of this project with what VSCode generates for you. HTH. |
Actually I began looking around that repo before I found your blog post. I had no idea VSCode would auto-generate projects with the Dockerfiles and all. They seem to not like using "discoverable" UI these days. |
Some googling suggests this is to do with gometalinter being now deprecated:
The text was updated successfully, but these errors were encountered: