Uh oh!
There was an error while loading. Please reload this page.
Dockerfile: Install a fixed version of gogoprotobuf - #2242
Conversation
This avoids build failures when gogoprotobuf is changed upstream. Signed-off-by: Euan Harris <euan.harris@docker.com>
It looks like they have just made a release, so we should consider jumping to v1.1.1 and regenerating in another pull request. Unfortunately this will be more work than just bumping the tag, as we get build failures with the newest version: |
euanh
commented
Jul 25, 2018
fcrisciani
commented
Jul 25, 2018
o fix the undefined message you have to bump the version of protobuf in the vendor from 1.0.0 to 1.1.1 The next problem looks like that the structure PortConfig is not anymore a valid key for a map: |
@fcrisciani Yes, I don't want to get up to the latest version in this PR - this is just to pin the version of the tools we use so that @selansen can get #2241 to build. Without this change, any PR to master will now fail in the |
This results in a XXX_unrecognized of type []byte to be created in the struct. As a side effect the struct can't be used as a map key anymore, resulting in a libnetwork build failure. Fix this by setting goproto_unrecognized_all=false which suppresses this field. Upstream doesn't have the problem because they have pinned an older version of gogo/protobuf: moby/libnetwork#2242 Author: Felix Geyer <fgeyer@debian.org> Gbp-Pq: Name libnetwork_proto_no_unrecognized_all.patch
Gogoprotobuf has changed upstream and now generates different output. Check out a specific commit to avoid this.
We may be able to do something like this with
go getin 1.11 with 'module aware mode':