You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .devcontainer/Dockerfile
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.238.1/containers/go/.devcontainer/base.Dockerfile
2
2
3
3
# [Choice] Go version (use -bullseye variants on local arm64/Apple Silicon): 1, 1.16, 1.17, 1-bullseye, 1.16-bullseye, 1.17-bullseye, 1-buster, 1.16-buster, 1.17-buster
4
-
ARG VARIANT="1.18-bullseye"
4
+
ARG VARIANT="1-bullseye"
5
5
FROM mcr.microsoft.com/vscode/devcontainers/go:0-${VARIANT}
Copy file name to clipboardExpand all lines: DEVELOPGUIDE.md
+4
Original file line number
Diff line number
Diff line change
@@ -27,3 +27,7 @@ Then test it locally.
27
27
All the binaries except `sealos` can be built anywhere since they have `CGO_ENABLED=0`. However, `sealos` needs to support overlay driver when running some subcommands like `images`, which relies on CGO. Therefore CGO is switched on when building `sealos`, making it impossible to build `sealos` binaries on platforms other than Linux.
28
28
29
29
> Both Makefile and GoReleaser in this project have this setting.
30
+
31
+
## Notes about go workspace
32
+
33
+
As sealos is using go1.18's workspace feature, once you add a new module, you need to run `go work usr -r .` at root directry to update the workspace synced.
0 commit comments