@@ -107,13 +107,13 @@ Try this now.
107
107
`dry-run-test` image.
108
108
109
109
```bash
110
- $ docker run --privileged --rm -ti -v `pwd`:/go/src/github.com/moby/moby dry-run-test /bin/bash
110
+ $ docker run --privileged --rm -ti -v `pwd`:/go/src/github.com/docker/docker dry-run-test /bin/bash
111
111
```
112
112
113
113
3. Run the tests using the `hack/make.sh` script.
114
114
115
115
```bash
116
- root@5f8630b873fe:/go/src/github.com/moby/moby # hack/make.sh dynbinary binary cross test-unit test-integration test-docker-py
116
+ root@5f8630b873fe:/go/src/github.com/docker/docker # hack/make.sh dynbinary binary cross test-unit test-integration test-docker-py
117
117
```
118
118
119
119
The tests run just as they did within your local host.
@@ -122,7 +122,7 @@ Try this now.
122
122
just the unit tests:
123
123
124
124
```bash
125
- root@5f8630b873fe:/go/src/github.com/moby/moby # hack/make.sh dynbinary binary cross test-unit
125
+ root@5f8630b873fe:/go/src/github.com/docker/docker # hack/make.sh dynbinary binary cross test-unit
126
126
```
127
127
128
128
Most test targets require that you build these precursor targets first:
@@ -170,7 +170,7 @@ $ TESTFLAGS='-check.f DockerSuite.TestBuild*' make test-integration
170
170
To run the same test inside your Docker development container, you do this:
171
171
172
172
` ` ` bash
173
- root@5f8630b873fe:/go/src/github.com/moby/moby # TESTFLAGS=' -check.f TestBuild*' hack/make.sh binary test-integration
173
+ root@5f8630b873fe:/go/src/github.com/docker/docker # TESTFLAGS=' -check.f TestBuild*' hack/make.sh binary test-integration
174
174
` ` `
175
175
176
176
# # Test the Windows binary against a Linux daemon
@@ -188,7 +188,7 @@ run a Bash terminal on Windows.
188
188
2. Change to the ` moby` source directory.
189
189
190
190
` ` ` bash
191
- $ cd /c/gopath/src/github.com/moby/moby
191
+ $ cd /c/gopath/src/github.com/docker/docker
192
192
` ` `
193
193
194
194
3. Set ` DOCKER_REMOTE_DAEMON` as follows:
0 commit comments