kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity
moby--moby/hack/dockerfile/binaries-commits

14 lines
497 B
Text
Raw Normal View History

Add expected 3rd party binaries commit ids to info Signed-off-by: Kenfe-Mickael Laventure <mickael.laventure@gmail.com>
2016-10-24 18:18:58 -04:00
#!/bin/sh
TOMLV_COMMIT=9baf8a8a9f2ed20a8e54160840c492f937eeaf9a
Bump runc to version a01dafd48bc1c7cc12bdb01206f9fea7dd6feb70 Signed-off-by: Kenfe-Mickael Laventure <mickael.laventure@gmail.com>
2017-02-22 14:45:43 -05:00
# When updating RUNC_COMMIT, also update runc in vendor.conf accordingly
Bump runc vendor Updates runc to b2567b37d7b75eb4cf325b77297b140ea686ce8f which removes some cross-repo dependencies. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
2017-11-13 08:55:03 -05:00
RUNC_COMMIT=b2567b37d7b75eb4cf325b77297b140ea686ce8f
Use commit-sha instead of tag for containerd The `docker info` command compares the installed version of containerd using a Git-sha. We currently use a tag for this, but that tag is not returned by the version-API of containerd, resulting in the `docker info` output to show: containerd version: 89623f28b87a6004d4b785663257362d1658a729 (expected: v1.0.0) This patch changes the `v1.0.0` tag to the commit that corresponds with the tag, so that the `docker info` output does not show the `expected:` string. This should be considered a temporary workaround; the check for the exact version of containerd that's installed was needed when we still used the 0.2.x branch, because it did not have stable releases yet. With containerd reaching 1.0, and using SemVer, we can likely do a comparison for "Major" version, or make this a "packaging" issue, and remove the check entirely (we can still _print_ the version that's installed if we think it's usefule). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-12-11 19:00:43 -05:00
CONTAINERD_COMMIT=89623f28b87a6004d4b785663257362d1658a729 # v1.0.0
Update Tini to fix photon build-rpm compilation errors Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2016-11-17 16:03:32 -05:00
TINI_COMMIT=949e6facb77383876aeff8a6944dde66b3089574
update docker-proxy to 7b2b1feb1de4817d522cc372af149ff48d25028e Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
2017-01-20 01:16:06 -05:00
LIBNETWORK_COMMIT=7b2b1feb1de4817d522cc372af149ff48d25028e
Bump vndr to a6e196d8b4b0cbbdc29aebdb20c59ac6926bb384 Includes a fix to cleanup unused vendor-directories Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2017-09-29 09:09:57 -04:00
VNDR_COMMIT=a6e196d8b4b0cbbdc29aebdb20c59ac6926bb384
Remove cmd/docker and other directories in cli/ in accordance with the new Moby project scope Starting with this commit, integration tests should no longer rely on the docker cli, they should be API tests instead. For the existing tests the scripts will use a frozen version of the docker cli with a DOCKER_API_VERSION frozen to 1.30, which should ensure that the CI remains green at all times. To help contributors develop and test manually with a modified docker cli, this commit also adds a DOCKER_CLI_PATH environment variable to the Makefile. This allows to set the path of a custom cli that will be available inside the development container and used to run the integration tests. Signed-off-by: Arnaud Porterie (icecrime) <arnaud.porterie@docker.com> Signed-off-by: Tibor Vass <tibor@docker.com>
2017-04-17 19:18:46 -04:00
Use gometalinter for linting Signed-off-by: Daniel Nephin <dnephin@docker.com>
2017-08-17 13:52:14 -04:00
# Linting
Add gosimple linter Update gometalinter Signed-off-by: Daniel Nephin <dnephin@docker.com>
2017-09-11 14:55:05 -04:00
GOMETALINTER_COMMIT=bfcc1d6942136fd86eb6f1a6fb328de8398fbd80
Copy permalink