Skip to content
This repository was archived by the owner on Oct 13, 2023. It is now read-only.

Conversation

@andrewhsu
Copy link
Contributor

Found differences between the engine and the cli vendor of engine in the docker-ce 17.06 branch. This PR will vendor github.com/docker/docker from components/engine dir.

Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
@andrewhsu andrewhsu changed the title vndr github.com/docker/docker from components/engine WIP vndr github.com/docker/docker from components/engine Jul 13, 2017
@@ -1,98 +0,0 @@
package opts
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was removed in moby/moby#33296

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i traced the sequence of events and it looks like this missing vendor change is a result of creating the docker-ce 17.06 branch before the cli was re-vendored. here is the sequence of events:


import (
"fmt"
"math/big"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@andrewhsu andrewhsu Aug 2, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same reason as #116 (comment), vendor was not in sync when 17.06 branch was created

@@ -1,111 +0,0 @@
package opts
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@andrewhsu andrewhsu Aug 2, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same reason as #116 (comment), vendor was not in sync when 17.06 branch was created

"github.com/docker/docker/pkg/ioutils"
)

const buffer32K = 32 * 1024
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#76

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change to components/cli was a result of a missing vendor update when #76 was cherry-picked to components/engine. should have been a separate commit in PR #76 to update the vendor

"github.com/pkg/errors"
)

type gitRepo struct {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change we definitely need to get in to fix stuff to do stuff

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cause of this discrepancy is same reason as #116 (comment): PR #100 should have had another commit to update components/cli/vendor

import "C"

// Termios is the Unix API for terminal I/O.
// It is passthrough for syscall.Termios in order to make it portable with
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@andrewhsu andrewhsu Aug 2, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same reason as #116 (comment), vendor was not in sync when 17.06 branch was created

// installCliPlatformFlags handles any platform specific flags for the service.
func (options *ServiceOptions) installCliPlatformFlags(flags *pflag.FlagSet) {
flags.BoolVar(&options.V2Only, "disable-legacy-registry", false, "Disable contacting legacy registries")
flags.BoolVar(&options.V2Only, "disable-legacy-registry", true, "Disable contacting legacy registries")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moby/moby#33629 (cherry-pick: #71)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cause of this discrepancy is same reason as #116 (comment): PR #71 should have had another commit to update components/cli/vendor

func (m *MountPoint) Setup(mountLabel string, rootUID, rootGID int) (path string, err error) {
// The, optional, checkFun parameter allows doing additional checking
// before creating the source directory on the host.
func (m *MountPoint) Setup(mountLabel string, rootUID, rootGID int, checkFun func(m *MountPoint) error) (path string, err error) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like PR #48 should have had another commit to update components/cli/vendor

@thaJeztah
Copy link
Member

I linked the related PR's either upstream (moby/moby) and/or the cherry-picks in components/engine

@andrewhsu andrewhsu added this to the 17.06.1 milestone Jul 14, 2017
Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

ping @andrewhsu still "WIP"?

@andrewhsu
Copy link
Contributor Author

I'm ok to have this PR in as a stop gap measure for now to get these guys in sync, but we have to think about a way to get the vendor dir updated on a more regular basis.

@andrewhsu andrewhsu changed the title WIP vndr github.com/docker/docker from components/engine vndr github.com/docker/docker from components/engine Jul 24, 2017
@andrewhsu
Copy link
Contributor Author

@tiborvass fyi

@thaJeztah
Copy link
Member

By now we probably should do the same again (various PR's were merged)?

@tiborvass
Copy link
Contributor

@tiborvass
Copy link
Contributor

I opened my version at #148

@andrewhsu
Copy link
Contributor Author

I've scrubbed all of the comments put in by @thaJeztah (thanks for digging into it) and found that the discrepancies between components/engine and components/cli/vendor/github.com/docker/docker are caused by one of two reasons:

  1. creating branch 17.06 when the upstream components docker/cli had not vendored moby/moby to keep in sync
  2. creating PRs to 17.06 that modify code in components/engine but with no corresponding sync to vendor in components/cli/vendor/github.com/docker/docker

For the first item, I suggest we setup a regular vendor sync in docker/cli repo to vendor changes from moby/moby /cc @dnephin

For the second item, I suggest we setup automatic vendor check to make sure code changes to components/engine are vendored into components/cli/vendor/github.com/docker/docker on PRs to docker-ce /cc @seemethere and I'd say #148 (thanks @tiborvass) is a step towards that direction.

So, I'm gong to close this PR in favor of #148 since it synced up the vendor directory a little later in time than this PR and caught 2 more vendor mismatches.

@andrewhsu andrewhsu closed this Aug 2, 2017
@andrewhsu andrewhsu removed this from the 17.06.1 milestone Aug 2, 2017
@andrewhsu andrewhsu deleted the sync-components branch August 2, 2017 06:49
@dnephin
Copy link
Contributor

dnephin commented Aug 2, 2017

Why is vendor mismatch a problem if the tests pass?

docker-jenkins pushed a commit that referenced this pull request Jul 3, 2018
[18.06] Remove Debian Jessie for arm64
Upstream-commit: 68e62582600895376c743e0e6b7e3df3478cd0b9
Component: packaging
docker-jenkins pushed a commit that referenced this pull request Nov 27, 2018
…al_templates

[18.09 backport] apparmor: allow receiving of signals from 'docker kill'
Upstream-commit: 12b8ec42b6ac60188ac48137677ee69ce98a3822
Component: engine
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants