mavenugo · October 13, 2016 23:42
diff --git a/gistify100198.go b/gistify100198.go
 # curl https://packages.docker.com/1.12/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 100 15534  100 15534    0     0  51863      0 --:--:-- --:--:-- --:--:-- 52303
 + sh -c 'sleep 3; yum -y -q install docker-engine'
 https://s3.amazonaws.com/packages.docker.com-staging/1.11/yum/repo/testing/centos/7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
 Trying other mirror.


 One of the configured repositories failed (Docker testing Repository),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable docker-testing-repo

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=docker-testing-repo.skip_if_unavailable=true

 failure: repodata/repomd.xml from docker-testing-repo: [Errno 256] No more mirrors to try.
 https://s3.amazonaws.com/packages.docker.com-staging/1.11/yum/repo/testing/centos/7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
	# curl https://packages.docker.com/1.12/install.sh \| bash
	% Total % Received % Xferd Average Speed Time Time Time Current
	Dload Upload Total Spent Left Speed
	100 15534 100 15534 0 0 51863 0 --:--:-- --:--:-- --:--:-- 52303
	+ sh -c 'sleep 3; yum -y -q install docker-engine'
	https://s3.amazonaws.com/packages.docker.com-staging/1.11/yum/repo/testing/centos/7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
	Trying other mirror.


	One of the configured repositories failed (Docker testing Repository),
	and yum doesn't have enough cached data to continue. At this point the only
	safe thing yum can do is fail. There are a few ways to work "fix" this:

	1. Contact the upstream for the repository and get them to fix the problem.

	2. Reconfigure the baseurl/etc. for the repository, to point to a working
	upstream. This is most often useful if you are using a newer
	distribution release than is supported by the repository (and the
	packages for the previous distribution release still work).

	3. Disable the repository, so yum won't use it by default. Yum will then
	just ignore the repository until you permanently enable it again or use
	--enablerepo for temporary usage:

	yum-config-manager --disable docker-testing-repo

	4. Configure the failing repository to be skipped, if it is unavailable.
	Note that yum will try to contact the repo. when it runs most commands,
	so will have to try and fail each time (and thus. yum will be be much
	slower). If it is a very temporary problem though, this is often a nice
	compromise:

	yum-config-manager --save --setopt=docker-testing-repo.skip_if_unavailable=true

	failure: repodata/repomd.xml from docker-testing-repo: [Errno 256] No more mirrors to try.
	https://s3.amazonaws.com/packages.docker.com-staging/1.11/yum/repo/testing/centos/7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden