Introduction

It was comfortable to build a Go development environment using Remote Containers, which is an extension of VS Code, so I will introduce it. I will omit the installation method of VS Code and Docker Desktop.

Remote Containers Remote Containers is an extension of VS Code's remote development features that is specialized for Docker. In addition, it seems that there are "Remote SSH" that connects remotely via SSH and "Remote WSL" that connects remotely using WSL (Windows Subsystem for Linux).

By connecting remotely from the local VS Code to the Docker container via VS Code Server, it is possible to develop in an environment separate from the local environment. In other words, it's a great feature that doesn't pollute the local environment while benefiting from code completion, etc., because everything is done on Docker.

Official site
As of October 2020, it will be a preview version.

Installation

Find and install Remote Containers from VS Code Extensions.

Initial setting

Open the menu with Ctrl + Shift + P and Select Remote-Containers: Add Development Cotainers Configuration Files ....

In my environment, I have already built the environment with docker-compose.yml and DockerFile, so I can make the initial settings based on those settings. You can also use the preset settings by selecting From a predefined container configuration definition .... This time, we will use the existing docker-compose file for initial setup.

.devcontainer When you make the initial settings, the .devcontainer folder is automatically created and under it. ・ Devcontainer.json ・ Docker-compose.yml Is automatically generated. devcontainer.json will be the configuration file.

Here, the current directory structure is as follows.

- .devcontainer
　├ devcontainer.json
  └ docker-compose.yml
- sample
└ Source code
- docker-compose.yml
- docker-compose.dev.yml
- Dockerfile 
- Dockerfile.dev

The automatically generated files are as follows.

`devcontainer.json`


// If you want to run as a non-root user in the container, see .devcontainer/docker-compose.yml.
{
	"name": "Existing Docker Compose (Extend)",

	// Update the 'dockerComposeFile' list if you have more compose files or use different names.
	// The .devcontainer/docker-compose.yml file contains any overrides you need/want to make.
	"dockerComposeFile": [
		"..\\docker-compose.dev.yml",
		"docker-compose.yml"
	],

	// The 'service' property is the name of the service for the container that VS Code should
	// use. Update this value and .devcontainer/docker-compose.yml to the real service name.
	"service": "sample",

	// The optional 'workspaceFolder' property is the path VS Code should open by default when
	// connected. This is typically a file mount in .devcontainer/docker-compose.yml
	"workspaceFolder": "/workspace",

	// Set *default* container specific settings.json values on container create.
	"settings": {
		"terminal.integrated.shell.linux": null
	},

	// Add the IDs of extensions you want installed when the container is created.
	"extensions": []

	// Use 'forwardPorts' to make a list of ports inside the container available locally.
	// "forwardPorts": [],

	// Uncomment the next line if you want start specific services in your Docker Compose config.
	// "runServices": [],

	// Uncomment the next line if you want to keep your containers running after VS Code shuts down.
	// "shutdownAction": "none",

	// Uncomment the next line to run commands after the container is created - for example installing curl.
	// "postCreateCommand": "apt-get update && apt-get install -y curl",

	// Uncomment to connect as a non-root user if you've added one. See https://aka.ms/vscode-remote/containers/non-root.
	// "remoteUser": "vscode"
}

`docker-compose.yml`


version: '3'
services:
  # Update this to the name of the service you want to work with in your docker-compose.yml file
  sample:
    # If you want add a non-root user to your Dockerfile, you can use the "remoteUser"
    # property in devcontainer.json to cause VS Code its sub-processes (terminals, tasks, 
    # debugging) to execute as the user. Uncomment the next line if you want the entire 
    # container to run as this user instead. Note that, on Linux, you may need to 
    # ensure the UID and GID of the container user you create matches your local user. 
    # See https://aka.ms/vscode-remote/containers/non-root for details.
    #
    # user: vscode

    # Uncomment if you want to override the service's Dockerfile to one in the .devcontainer 
    # folder. Note that the path of the Dockerfile and context is relative to the *primary* 
    # docker-compose.yml file (the first in the devcontainer.json "dockerComposeFile"
    # array). The sample below assumes your primary file is in the root of your project.
    #
    # build:
    #   context: .
    #   dockerfile: .devcontainer/Dockerfile
    
    volumes:
      # Update this to wherever you want VS Code to mount the folder of your project
      - .:/workspace:cached

      # Uncomment the next line to use Docker from inside the container. See https://aka.ms/vscode-remote/samples/docker-from-docker-compose for details.
      # - /var/run/docker.sock:/var/run/docker.sock 

    # Uncomment the next four lines if you will use a ptrace-based debugger like C++, Go, and Rust.
    # cap_add:
    #   - SYS_PTRACE
    # security_opt:
    #   - seccomp:unconfined

    # Overrides default command so things don't shut down after the process ends.
    command: /bin/sh -c "while sleep 1000; do :; done"

Although the file was generated once, I didn't like the double management of docker-compose.yml, so I moved everything to docker-compose.yml under .devcontainer.

Settings for Go

We will add settings for developing Go.

extensions Locally installed VS Code extensions are not available inside the remote container, so set the extensions to be installed automatically when the container starts. Put in Go extensions. This string can be obtained from the right-click Copy Extension Id in the extension list.

`devcontainer.json`


	"extensions": [
		"golang.go"
	]

settings Since gopls is used, add the settings by referring to github. Regarding Gomod setting (GO111MODULE), it is no longer necessary after 1.13, but if you do not set it, an error will appear in the import statement, so set it.

`devcontainer.json`


"settings": {
		"terminal.integrated.shell.linux": "/bin/bash",
		"go.useLanguageServer": true,
		"[go]": {
			"editor.formatOnSave": true,
			"editor.codeActionsOnSave": {
				"source.organizeImports": true,
			},
			// Optional: Disable snippets, as they conflict with completion ranking.
			"editor.snippetSuggestions": "none",
		},
		"[go.mod]": {
			"editor.formatOnSave": true,
			"editor.codeActionsOnSave": {
				"source.organizeImports": true,
			},
		},
		"gopls": {
			// Add parameter placeholders when completing a function.
			"usePlaceholders": true,
			// If true, enable additional analyses with staticcheck.
			// Warning: This will significantly increase memory usage.
			"staticcheck": false,
		},
		"go.toolsEnvVars":{
			"GO111MODULE":"on"
		}
	}

workspaceFolder Set the workspace when starting the remote container. On the docker-compose.yml side, the volume will be mounted under / go / src /, so change the workspace accordingly.

`devcontainer.json`


"workspaceFolder": "/go/src/sample",

Setup is completed.

Start-up

Actually start the container. Select Remote-Containers: Reopen in Container from Ctrl + Shift + P

At the first startup, the tools are not installed in / go / bin, so install them.

Since gopls is used, install it from the notification below, or Run go get -v golang.org/x/tools/gopls

For other tools, install other than gocode and gocode-gomod from Go: Install / Update Tools.

I was able to confirm that everything was installed under / go / bin.

At this point, you can develop on the container. Of course, it is managed on a container-by-container basis, so if you delete a container, the installed one will disappear, so you will need to reconfigure it.

debug

You can also debug inside the container. Create a .vscode folder in the same directory as the mounted source code and create a launch.json.

`launch.json`


{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Remote",
            "type": "go",
            "request": "launch",
            "host": "localhost",
            "program": "${workspaceRoot}",
            "args": []
        }
    ]
}

Summary

I will describe the file that was finally created. I hope you find it helpful.

`devcontianer.json`


{
	"name": "Existing Docker Compose (Extend)",
	"dockerComposeFile": [
		"docker-compose.yml"
	],
	"service": "sample",
	"workspaceFolder": "/go/src/sample",
	"settings": {
		"terminal.integrated.shell.linux": "/bin/bash",
		"go.useLanguageServer": true,
		"[go]": {
			"editor.formatOnSave": true,
			"editor.codeActionsOnSave": {
				"source.organizeImports": true,
			},
			"editor.snippetSuggestions": "none",
		},
		"[go.mod]": {
			"editor.formatOnSave": true,
			"editor.codeActionsOnSave": {
				"source.organizeImports": true,
			},
		},
		"gopls": {
			"usePlaceholders": true,
			"staticcheck": false,
		},
		"go.toolsEnvVars":{
			"GO111MODULE":"on"
		}
	},
	"extensions": [
		"golang.go"
	]
}

`docker-compose.yml`


version: '3'
services:
  # Update this to the name of the service you want to work with in your docker-compose.yml file
  sample:
    image: golang:1.14
    volumes:
      - ./../:/go/src/:cached
    tty: true
    environment:
      - MYSQL_CONNECTION_STRING=${CONNECTION_STRING}
    networks:
      - default
      - db-network
networks:
  db-network:
    external: true

reference

--Go study (1) Mac ＋ VSCode ＋ Go environment setting: https://qiita.com/oruharo/items/545378eae5c707f717ed

VS Code Dev Container Guidebook：https://techbookfest.org/product/4696850535809024?productVariantID=5428870601768960

[DOCKER] Build a Go development environment with VS Code's Remote Containers

Introduction

Installation

Initial setting

devcontainer.json

docker-compose.yml

Settings for Go

devcontainer.json

devcontainer.json

devcontainer.json

Start-up

debug

launch.json

Summary

devcontianer.json

docker-compose.yml

reference

`devcontainer.json`

`docker-compose.yml`

`devcontainer.json`

`devcontainer.json`

`devcontainer.json`

`launch.json`

`devcontianer.json`

`docker-compose.yml`