fix some references docker/swarmkit -> moby/swarmkit

thaJeztah · thaJeztah · commit 3e6e51842fc0 · 2022-11-21T21:21:29.000+01:00
Signed-off-by: Sebastiaan van Stijn &lt;github@gone.nl&gt;
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -6,6 +6,7 @@ jobs:
     # other environment variables (although the working directory can use the `~` character,
     # but environment variables cannot), so to avoid having to override the GOPATH for every
     # run command, just hard code in the directory to be CircleCI expects it to be.
+    # FIXME: this still needs to be docker/swarmkit, as that's how it's referenced in protobuf
     working_directory: /home/circleci/.go_workspace/src/github.com/docker/swarmkit
     environment:
       # Needed to install go
@@ -18,7 +19,7 @@ jobs:
 
     # Note(cyli): We create a tmpfs mount to be used for temporary files created by tests
     # to mitigate the excessive I/O latencies that sometimes cause the tests to fail.
-    # See https://github.com/docker/swarmkit/pull/2254.
+    # See https://github.com/moby/swarmkit/pull/2254.
 
     # There is no way to mount tmpfs volumes in the docker executor, so we are using
     # the machine executor. However, this incur a performance overhead
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,6 @@
 <!--
 Please make sure you've read and understood our contributing guidelines;
-https://github.com/docker/swarmkit/blob/master/CONTRIBUTING.md
+https://github.com/moby/swarmkit/blob/master/CONTRIBUTING.md
 
 ** Make sure all your commits include a signature generated with `git commit -s` **
 
diff --git a/BUILDING.md b/BUILDING.md
@@ -7,18 +7,18 @@ When setup correctly, you should have a GOROOT and GOPATH set in the environment
 After you set up the Go development environment, use `go get` to check out
 `swarmkit`:
 
-    go get -d github.com/docker/swarmkit
+    go get -d github.com/moby/swarmkit/v2@latest
 
 This command installs the source repository into the `GOPATH`.
 
 It is not mandatory to use `go get` to checkout the SwarmKit project. However,
 for these instructions to work, you need to check out the project to the
-correct subdirectory of the `GOPATH`: `$GOPATH/src/github.com/docker/swarmkit`.
+correct subdirectory of the `GOPATH`: `$GOPATH/src/github.com/moby/swarmkit`.
 
 ### Repeatable Builds
 
 For the full development experience, one should `cd` into
-`$GOPATH/src/github.com/docker/swarmkit`. From there, the regular `go`
+`$GOPATH/src/github.com/moby/swarmkit`. From there, the regular `go`
 commands, such as `go test`, should work per package (please see
 [Developing](#developing) if they don't work).
 
@@ -41,35 +41,35 @@ build:
     🐳 vet
     🐳 lint
     🐳 build
-    github.com/docker/swarmkit
-    github.com/docker/swarmkit/vendor/github.com/davecgh/go-spew/spew
-    github.com/docker/swarmkit/vendor/github.com/pmezard/go-difflib/difflib
-    github.com/docker/swarmkit/cmd/protoc-gen-gogoswarm
-    github.com/docker/swarmkit/cmd/swarm-bench
-    github.com/docker/swarmkit/cmd/swarmctl
-    github.com/docker/swarmkit/vendor/github.com/stretchr/testify/assert
-    github.com/docker/swarmkit/ca/testutils
-    github.com/docker/swarmkit/cmd/swarmd
-    github.com/docker/swarmkit/vendor/code.cloudfoundry.org/clock/fakeclock
-    github.com/docker/swarmkit/vendor/github.com/stretchr/testify/require
-    github.com/docker/swarmkit/manager/state/raft/testutils
-    github.com/docker/swarmkit/manager/testcluster
-    github.com/docker/swarmkit/protobuf/plugin/deepcopy/test
-    github.com/docker/swarmkit/protobuf/plugin/raftproxy/test
+    github.com/moby/swarmkit
+    github.com/moby/swarmkit/vendor/github.com/davecgh/go-spew/spew
+    github.com/moby/swarmkit/vendor/github.com/pmezard/go-difflib/difflib
+    github.com/moby/swarmkit/cmd/protoc-gen-gogoswarm
+    github.com/moby/swarmkit/cmd/swarm-bench
+    github.com/moby/swarmkit/cmd/swarmctl
+    github.com/moby/swarmkit/vendor/github.com/stretchr/testify/assert
+    github.com/moby/swarmkit/ca/testutils
+    github.com/moby/swarmkit/cmd/swarmd
+    github.com/moby/swarmkit/vendor/code.cloudfoundry.org/clock/fakeclock
+    github.com/moby/swarmkit/vendor/github.com/stretchr/testify/require
+    github.com/moby/swarmkit/manager/state/raft/testutils
+    github.com/moby/swarmkit/manager/testcluster
+    github.com/moby/swarmkit/protobuf/plugin/deepcopy/test
+    github.com/moby/swarmkit/protobuf/plugin/raftproxy/test
     🐳 test
-    ?       github.com/docker/swarmkit      [no test files]
-    ?       github.com/docker/swarmkit      [no test files]
-    ok      github.com/docker/swarmkit/agent        2.264s
-    ok      github.com/docker/swarmkit/agent/exec   1.055s
-    ok      github.com/docker/swarmkit/agent/exec/container 1.094s
-    ?       github.com/docker/swarmkit/api  [no test files]
-    ?       github.com/docker/swarmkit/api/duration [no test files]
-    ?       github.com/docker/swarmkit/api/timestamp        [no test files]
-    ok      github.com/docker/swarmkit/ca   15.634s
+    ?       github.com/moby/swarmkit      [no test files]
+    ?       github.com/moby/swarmkit      [no test files]
+    ok      github.com/moby/swarmkit/agent        2.264s
+    ok      github.com/moby/swarmkit/agent/exec   1.055s
+    ok      github.com/moby/swarmkit/agent/exec/container 1.094s
+    ?       github.com/moby/swarmkit/api  [no test files]
+    ?       github.com/moby/swarmkit/api/duration [no test files]
+    ?       github.com/moby/swarmkit/api/timestamp        [no test files]
+    ok      github.com/moby/swarmkit/ca   15.634s
     ...
-    ok      github.com/docker/swarmkit/protobuf/plugin/raftproxy/test       1.084s
-    ok      github.com/docker/swarmkit/protobuf/ptypes      1.025s
-    ?       github.com/docker/swarmkit/version      [no test files]
+    ok      github.com/moby/swarmkit/protobuf/plugin/raftproxy/test       1.084s
+    ok      github.com/moby/swarmkit/protobuf/ptypes      1.025s
+    ?       github.com/moby/swarmkit/version      [no test files]
 
 The above provides a repeatable build using the contents of the vendored
 `./vendor` directory. This includes formatting, vetting, linting, building,
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -37,7 +37,7 @@ A great way to contribute to the project is to send a detailed report when you
 encounter an issue. We always appreciate a well-written, thorough bug report,
 and will thank you for it!
 
-Check that [our issue database](https://github.com/docker/swarmkit/issues)
+Check that [our issue database](https://github.com/moby/swarmkit/issues)
 doesn't already include that problem or suggestion before submitting an issue.
 If you find a match, you can use the "subscribe" button to get notified on
 updates. Do *not* leave random "+1" or "I have this too" comments, as they
@@ -64,7 +64,7 @@ This section gives the experienced contributor some tips and guidelines.
 
 Not sure if that typo is worth a pull request? Found a bug and know how to fix
 it? Do it! We will appreciate it. Any significant improvement should be
-documented as [a GitHub issue](https://github.com/docker/swarmkit/issues) before
+documented as [a GitHub issue](https://github.com/moby/swarmkit/issues) before
 anybody starts working on it.
 
 We are always thrilled to receive pull requests. We do our best to process them
diff --git a/MAINTAINERS b/MAINTAINERS
@@ -1,5 +1,5 @@
 #
-# This file describes who runs the docker/swarmkit project and how.
+# This file describes who runs the moby/swarmkit project and how.
 # This file is compiled into the MAINTAINERS file in docker/opensource.
 #
 [Org]
diff --git a/README.md b/README.md
@@ -1,9 +1,9 @@
-# [SwarmKit](https://github.com/docker/swarmkit)
+# [SwarmKit](https://github.com/moby/swarmkit)
 
-[![GoDoc](https://godoc.org/github.com/docker/swarmkit?status.svg)](https://godoc.org/github.com/docker/swarmkit)
-[![Circle CI](https://circleci.com/gh/docker/swarmkit.svg?style=shield&circle-token=a7bf494e28963703a59de71cf19b73ad546058a7)](https://circleci.com/gh/docker/swarmkit)
-[![codecov.io](https://codecov.io/github/docker/swarmkit/coverage.svg?branch=master&token=LqD1dzTjsN)](https://codecov.io/github/docker/swarmkit?branch=master)
-[![Badge Badge](http://doyouevenbadge.com/github.com/docker/swarmkit)](http://doyouevenbadge.com/report/github.com/docker/swarmkit)
+[![GoDoc](https://godoc.org/github.com/moby/swarmkit?status.svg)](https://godoc.org/github.com/moby/swarmkit)
+[![Circle CI](https://circleci.com/gh/moby/swarmkit.svg?style=shield&circle-token=a7bf494e28963703a59de71cf19b73ad546058a7)](https://circleci.com/gh/moby/swarmkit)
+[![codecov.io](https://codecov.io/github/moby/swarmkit/coverage.svg?branch=master&token=LqD1dzTjsN)](https://codecov.io/github/moby/swarmkit?branch=master)
+[![Badge Badge](http://doyouevenbadge.com/github.com/moby/swarmkit)](http://doyouevenbadge.com/report/github.com/moby/swarmkit)
 
 *SwarmKit* is a toolkit for orchestrating distributed systems at any scale. It includes primitives for node discovery, raft-based consensus, task scheduling and more.
 
diff --git a/agent/exec/controller_stub.go b/agent/exec/controller_stub.go
@@ -37,7 +37,7 @@ func (sc *StubController) called() {
 	if !ok {
 		panic("Failed to find caller of function")
 	}
-	// longName looks like 'github.com/docker/swarmkit/agent/exec.(*StubController).Prepare:1'
+	// longName looks like 'github.com/moby/swarmkit/agent/exec.(*StubController).Prepare:1'
 	longName := runtime.FuncForPC(pc).Name()
 	parts := strings.Split(longName, ".")
 	tail := strings.Split(parts[len(parts)-1], ":")
diff --git a/agent/exec/dockerapi/docker_client_stub.go b/agent/exec/dockerapi/docker_client_stub.go
@@ -44,7 +44,7 @@ func (sa *StubAPIClient) called() {
 	if !ok {
 		panic("failed to update counts")
 	}
-	// longName looks like 'github.com/docker/swarmkit/agent/exec.(*StubController).Prepare:1'
+	// longName looks like 'github.com/moby/swarmkit/agent/exec.(*StubController).Prepare:1'
 	longName := runtime.FuncForPC(pc).Name()
 	parts := strings.Split(longName, ".")
 	tail := strings.Split(parts[len(parts)-1], ":")
diff --git a/agent/exec/executor.go b/agent/exec/executor.go
@@ -112,9 +112,9 @@ type VolumesManager interface {
 	Plugins() VolumePluginManager
 }
 
-// PluginManager is the interface for accessing the volume plugin manager from
+// VolumePluginManager is the interface for accessing the volume plugin manager from
 // the executor. This is identical to
-// github.com/docker/swarmkit/agent/csi/plugin.PluginManager, except the former
+// github.com/moby/swarmkit/agent/csi/plugin.PluginManager, except the former
 // also includes a Get method for the VolumesManager to use. This does not
 // contain that Get method, to avoid having to import the Plugin type, and
 // because in this context, it is not needed.
diff --git a/cmd/external-ca-example/README.md b/cmd/external-ca-example/README.md
@@ -3,7 +3,7 @@
 To get started, build and install the go program in this directory:
 
 ```
-$ go install github.com/docker/swarmkit/cmd/external-ca-example
+$ go install github.com/moby/swarmkit/v2/cmd/external-ca-example@latest
 ```
 
 Now, run `external-ca-example`:
diff --git a/design/generic_resources.md b/design/generic_resources.md
@@ -57,15 +57,15 @@ to be cluster wide in order to satisfy other use cases (e.g: pool of licenses)
 
 ## Related Issues
 
-  * [Support abstract resource](https://github.com/docker/swarmkit/issues/594)
+  * [Support abstract resource](https://github.com/moby/swarmkit/issues/594)
   * [Add new node filter to scheduler](https://github.com/docker/swarm/issues/2223)
-  * [Add support for devices](https://github.com/docker/swarmkit/issues/1244)
-  * [Resource Control](https://github.com/docker/swarmkit/issues/211)
+  * [Add support for devices](https://github.com/moby/swarmkit/issues/1244)
+  * [Resource Control](https://github.com/moby/swarmkit/issues/211)
   * [NVIDIA GPU support](https://github.com/docker/docker/issues/23917)
   * [Does Docker have plan to support allocating GPU](https://github.com/docker/docker/issues/24582)
   * [Docker Swarm to orchestrate "Swarm Cluster" which supports GPU](https://github.com/docker/docker/issues/24750)
   * [Use accelerator in docker container](https://github.com/docker/docker/issues/28642)
-  * [Specify resource selectors](https://github.com/docker/swarmkit/issues/206)
+  * [Specify resource selectors](https://github.com/moby/swarmkit/issues/206)
 
 ## Objectives
 
diff --git a/design/orchestrators.md b/design/orchestrators.md
@@ -81,7 +81,7 @@ number of tasks running on multiple nodes, it prefers to remove tasks that
 aren't running (in terms of observed state) over tasks that are currently
 running. Note that scale-down decisions are made by the orchestrator, and don't
 quite match the state the scheduler would arrive at when scaling up. This is an
-area for future improvement; see https://github.com/docker/swarmkit/issues/2320
+area for future improvement; see https://github.com/moby/swarmkit/issues/2320
 for more details.
 
 In both of these cases, and also in the case where the number of replicas is
diff --git a/design/raft.md b/design/raft.md
@@ -3,7 +3,7 @@
 SwarmKit uses the Raft consensus protocol to synchronize state between manager
 nodes and support high availability. The lowest level portions of this are
 provided by the `go.etcd.io/etcd/raft/v3` package. SwarmKit's
-`github.com/docker/swarmkit/manager/state/raft` package builds a complete
+`github.com/moby/swarmkit/manager/state/raft` package builds a complete
 solution on top of this, adding things like saving and loading state on disk,
 an RPC layer so nodes can pass Raft messages over a network, and dynamic cluster
 membership.
@@ -201,7 +201,7 @@ invoke RPCs on the leader, so the communication would only happen in one
 direction. It would normally be impossible for the node to catch up. With
 `ResolveAddress`, it can query other cluster members for the leader's address,
 and restore two-way communication. See
-https://github.com/docker/swarmkit/issues/436 more details on this situation.
+https://github.com/moby/swarmkit/issues/436 more details on this situation.
 
 SwarmKit's `raft/transport` package abstracts the mechanism for keeping track of
 peers, and sending messages to them over gRPC in a specific message order.
diff --git a/design/store.md b/design/store.md
@@ -218,7 +218,7 @@ There is a watch server that provides a very similar interface to the `Watch`
 call. See `api/watch.proto` for the relevant protobuf definitions.
 
 A full gRPC API for the store has been proposed, but not yet merged at the time
-this document was written. See https://github.com/docker/swarmkit/pull/1998 for
+this document was written. See https://github.com/moby/swarmkit/pull/1998 for
 draft code. In this proposal, the gRPC store API did not support full
 transactions, but did allow creations and updates to happen in atomic sets.
 Implementing full transactions over gRPC presents some challenges, because of

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,5 @@`
`1`	`1`	`#`
`2`		`-# This file describes who runs the docker/swarmkit project and how.`
	`2`	`+# This file describes who runs the moby/swarmkit project and how.`
`3`	`3`	`# This file is compiled into the MAINTAINERS file in docker/opensource.`
`4`	`4`	`#`
`5`	`5`	`[Org]`
Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ func (sc *StubController) called() {`
`37`	`37`	`if !ok {`
`38`	`38`	`panic("Failed to find caller of function")`
`39`	`39`	`}`
`40`		`- // longName looks like 'github.com/docker/swarmkit/agent/exec.(*StubController).Prepare:1'`
	`40`	`+ // longName looks like 'github.com/moby/swarmkit/agent/exec.(*StubController).Prepare:1'`
`41`	`41`	`longName := runtime.FuncForPC(pc).Name()`
`42`	`42`	`parts := strings.Split(longName, ".")`
`43`	`43`	`tail := strings.Split(parts[len(parts)-1], ":")`
Original file line number	Diff line number	Diff line change
`@@ -44,7 +44,7 @@ func (sa *StubAPIClient) called() {`
`44`	`44`	`if !ok {`
`45`	`45`	`panic("failed to update counts")`
`46`	`46`	`}`
`47`		`- // longName looks like 'github.com/docker/swarmkit/agent/exec.(*StubController).Prepare:1'`
	`47`	`+ // longName looks like 'github.com/moby/swarmkit/agent/exec.(*StubController).Prepare:1'`
`48`	`48`	`longName := runtime.FuncForPC(pc).Name()`
`49`	`49`	`parts := strings.Split(longName, ".")`
`50`	`50`	`tail := strings.Split(parts[len(parts)-1], ":")`