Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-11-04 01:30:15 +01:00
Code Issues Projects Releases Wiki Activity
4af542d6d0
harbor/make/photon/notary/binary.Dockerfile

28 lines
1.2 KiB
Docker
Raw Normal View History

roll back go for notary binary Fixes #14932 Harbor recompiles the notary v0.6.1 with go 1.15 from v2.2.0, which introduces an break change that leads to notary key not found after migration. [Root cause] Notary v0.6.1 consumed an old version dvsekhvalnov/jose2, which is not compatible with go 1.15. [References] https://github.com/dvsekhvalnov/jose2go/issues/26 https://github.com/golang/go/issues/41089 [Resolve] To resolve this issue, we have to roll back go vesrion to v1.14 for notary v0.6.1 binary and keep it until upstream have a patch release to support go 1.15 or above. [Break change] If you pushed and signed image using Harbor v2.2.0 ~ v2.2.2 and created new repository key in notary, you will encouter the same issue after migrate to v2.2.3(or above) or v2.3.1(or above) because of the go version downgrade. We will have a FAQ to help you to resovle this particular scenario. The influence path of the particular case: Harbor v2.1.0(or lower) --> [v2.2.0 ~ v2.2.2] --> v2.2.3(or above) Harbor v2.1.0(or lower) --> v2.3.0 --> v2.3.1(or above) The non influence path of the paticular case: Harbor v2.1.0(or lower) --> v2.2.3(or above) Harbor v2.1.0(or lower) --> v2.3.1(or above) [Fix in Version] Harbor v2.2.3 or above Harbor v2.3.1 or above [Note] If you're a heavy user of notary, avoid using v2.2.0, v2.2.1, v2.2.2 and v2.3.0, and use the fixed version for instead. Signed-off-by: Wang Yan <wangyan@vmware.com>
2021-06-29 09:08:52 +02:00
FROM golang:1.14.15
automate scripts for notary(signer/server) docker images bases on photon 1.0, code is not based on 0.5.0 remove the binary temp folder, just keep on binary path.
2017-09-26 11:14:13 +02:00
Bump up the migrate tool of notary fixes #5863 The migrate binary that we include in notary is quite out dated. Additionally it introduced a breaking change, more details see #5863 In this commit a go program was added to workaround this issue to ensure the migration process works, and refined bootstrap scripts and make process accordingly. Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-02-19 05:51:37 +01:00
ARG NOTARY_VERSION
ARG MIGRATE_VERSION
RUN test -n "$NOTARY_VERSION"
RUN test -n "$MIGRATE_VERSION"
Unify images tags and build process
2017-12-09 19:53:12 +01:00
ENV NOTARYPKG github.com/theupdateframework/notary
Bump up the migrate tool of notary fixes #5863 The migrate binary that we include in notary is quite out dated. Additionally it introduced a breaking change, more details see #5863 In this commit a go program was added to workaround this issue to ensure the migration process works, and refined bootstrap scripts and make process accordingly. Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-02-19 05:51:37 +01:00
ENV MIGRATEPKG github.com/golang-migrate/migrate
automate scripts for notary(signer/server) docker images bases on photon 1.0, code is not based on 0.5.0 remove the binary temp folder, just keep on binary path.
2017-09-26 11:14:13 +02:00
Bump up the migrate tool of notary fixes #5863 The migrate binary that we include in notary is quite out dated. Additionally it introduced a breaking change, more details see #5863 In this commit a go program was added to workaround this issue to ensure the migration process works, and refined bootstrap scripts and make process accordingly. Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-02-19 05:51:37 +01:00
RUN git clone -b $NOTARY_VERSION https://github.com/theupdateframework/notary.git /go/src/${NOTARYPKG}
automate scripts for notary(signer/server) docker images bases on photon 1.0, code is not based on 0.5.0 remove the binary temp folder, just keep on binary path.
2017-09-26 11:14:13 +02:00
WORKDIR /go/src/${NOTARYPKG}
Unify images tags and build process
2017-12-09 19:53:12 +01:00
RUN go install -tags pkcs11 \
-ldflags "-w -X ${NOTARYPKG}/version.GitCommit=`git rev-parse --short HEAD` -X ${NOTARYPKG}/version.NotaryVersion=`cat NOTARY_VERSION`" ${NOTARYPKG}/cmd/notary-server
automate scripts for notary(signer/server) docker images bases on photon 1.0, code is not based on 0.5.0 remove the binary temp folder, just keep on binary path.
2017-09-26 11:14:13 +02:00
Unify images tags and build process
2017-12-09 19:53:12 +01:00
RUN go install -tags pkcs11 \
-ldflags "-w -X ${NOTARYPKG}/version.GitCommit=`git rev-parse --short HEAD` -X ${NOTARYPKG}/version.NotaryVersion=`cat NOTARY_VERSION`" ${NOTARYPKG}/cmd/notary-signer
Bump up the migrate tool of notary fixes #5863 The migrate binary that we include in notary is quite out dated. Additionally it introduced a breaking change, more details see #5863 In this commit a go program was added to workaround this issue to ensure the migration process works, and refined bootstrap scripts and make process accordingly. Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-02-19 05:51:37 +01:00
RUN cp -r /go/src/${NOTARYPKG}/migrations/ /
RUN git clone -b $MIGRATE_VERSION https://github.com/golang-migrate/migrate /go/src/${MIGRATEPKG}
WORKDIR /go/src/${MIGRATEPKG}
Bump up the go-migrate (#13914) Bump it up to v4.11.0 to be consistent with harbor-core Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2021-01-11 12:08:17 +01:00
ENV DATABASES="postgres mysql redshift cassandra spanner cockroachdb"
Bump up the migrate tool of notary fixes #5863 The migrate binary that we include in notary is quite out dated. Additionally it introduced a breaking change, more details see #5863 In this commit a go program was added to workaround this issue to ensure the migration process works, and refined bootstrap scripts and make process accordingly. Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-02-19 05:51:37 +01:00
ENV SOURCES="file go_bindata github aws_s3 google_cloud_storage"
RUN go install -tags "$DATABASES $SOURCES" -ldflags="-X main.Version=${MIGRATE_VERSION}" ${MIGRATEPKG}/cli && mv /go/bin/cli /go/bin/migrate
Reference in New Issue Copy Permalink