Try Out Development Containers: Go

A development container is a running Docker container with a well-defined tool/runtime stack and its prerequisites. You can try out development containers with GitHub Codespaces or Visual Studio Code Remote - Containers.

This is a sample project that lets you try out either option in a few easy steps. We have a variety of other vscode-remote-try-* sample projects, too.

Note: If you already have a Codespace or dev container, you can jump to the Things to try section.

Setting up the development container

GitHub Codespaces

Follow these steps to open this sample in a Codespace:

Click the Code drop-down menu and select the Open with Codespaces option.
Select + New codespace at the bottom on the pane.

For more info, check out the GitHub documentation.

VS Code Remote - Containers

Follow these steps to open this sample in a container using the VS Code Remote - Containers extension:

If this is your first time using a development container, please ensure your system meets the pre-reqs (i.e. have Docker installed) in the getting started steps.
To use this repository, you can either open the repository in an isolated Docker volume:
- Press F1 and select the Remote-Containers: Try a Sample... command.
- Choose the "Go" sample, wait for the container to start, and try things out!
  
  Note: Under the hood, this will use the Remote-Containers: Clone Repository in Container Volume... command to clone the source code in a Docker volume instead of the local filesystem. Volumes are the preferred mechanism for persisting container data.
Or open a locally cloned copy of the code:
- Clone this repository to your local filesystem.
- Press F1 and select the Remote-Containers: Open Folder in Container... command.
- Select the cloned copy of this folder, wait for the container to start, and try things out!

Things to try

Once you have this sample opened, you'll be able to work with it like you would locally.

Note: This container runs as a non-root user with sudo access by default. Comment out "remoteUser": "vscode" in .devcontainer/devcontainer.json if you'd prefer to run as root.

Some things to try:

Edit:
- Open server.go
- Try adding some code and check out the language features.
- Notice the Go extension is already installed in the container since the .devcontainer/devcontainer.json lists "golang.Go" as an extension to install automatically when the container is created.
Terminal: Press ctrl+shift+` and type uname and other Linux commands from the terminal window.
Build, Run, and Debug:
- Open server.go
- Add a breakpoint (e.g. on line 22).
- Press F5 to launch the app in the container.
- Once the breakpoint is hit, try hovering over variables, examining locals, and more.
- Continue (F5). You can connect to the server in the container by either:
  - Clicking on Open in Browser in the notification telling you: Your service running on port 9000 is available.
  - Clicking the globe icon in the 'Ports' view. The 'Ports' view gives you an organized table of your forwarded ports, and you can get there by clicking on the "1" in the status bar, which means your app has 1 forwarded port.
- Notice port 9000 in the 'Ports' view is labeled "Hello Remote World." In devcontainer.json, you can set "portsAttributes", such as a label for your forwarded ports and the action to be taken when the port is autoforwarded.
Note: In Remote - Containers, you can access your app at http://localhost:9000 in a local browser. But in a browser-based Codespace, you must click the link from the notification or the Ports view so that the service handles port forwarding in the browser and generates the correct URL.
Rebuild or update your container:

You may want to make changes to your container, such as installing a different version of a software or forwarding a new port. You'll rebuild your container for your changes to take effect.

Open browser automatically: As an example change, let's update the portsAttributes in the .devcontainer/devcontainer.json file to open a browser when our port is automatically forwarded.
- Open the .devcontainer/devcontainer.json file.
- Modify the "onAutoForward" attribute in your portsAttributes from "notify" to "openBrowser".
- Press F1 and select the Remote-Containers: Rebuild Container or Codespaces: Rebuild Container command so the modifications are picked up.
Refactoring - rename:
- Open hello.go, select method name Hello press F1 and run the Rename Symbol command.
Refactoring - extract:
- Open hello.go and select string, press F1 and run the Go: Extract to variable command.
- Open hello.go and select line with return statement, press F1 and run the Go: Extract to function command.
Generate tests:
- Open hello.go and press F1 and run the Go: Generate Unit Tests For File command.
- Implement a test case: Open file hello_test.go and edit the line with the TODO comment: {"hello without name", "Hello, "},
- You can toggle between implementation file and test file with press F1 and run the Go: Toggle Test File
- Tests can also run as benchmarks: Open file hello_test.go, press F1 and run the Go: Benchmark File
Stub generation: ( details)
- define a struct type mock struct {}, enter a new line , press F1 and run the Go: Generate interface stubs command.
- edit command m *mock http.ResponseWriter
Fill structs: (details)
- Open hello.go and select User{} of variable asignment, press F1 and run the Go: Fill struct command.
Add json tags to structs: (details)

Open hello.go and go with cursor in to a struct, press F1 and run the Go: Add Tags To Struct Fields command.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.