harbor/make/dev/adminserver/Dockerfile

FROM golang:1.9.2

MAINTAINER yinw@vmware.com

COPY . /go/src/github.com/goharbor/harbor

WORKDIR /go/src/github.com/goharbor/harbor/src/adminserver

RUN go build -a -o /go/bin/harbor_adminserver \
    && chmod u+x /go/bin/harbor_adminserver 

COPY ./make/migrations /go/bin/migrations
WORKDIR /go/bin/
ENTRYPOINT ["/go/bin/harbor_adminserver"]
Reduce the output of build. The following are done to avoid travis-ci failing due to too much log size. 1) Update Makefile and scripts to make go build less verbose. 2) Make tdnf less verbose 2018-02-27 08:01:14 +01:00			`FROM golang:1.9.2`
configure harbor 2016-12-30 11:04:01 +01:00
			`MAINTAINER yinw@vmware.com`

Update import path in go code vmware -> goharbor Signed-off-by: Daniel Jiang <jiangd@vmware.com> 2018-08-23 09:02:20 +02:00			`COPY . /go/src/github.com/goharbor/harbor`
configure harbor 2016-12-30 11:04:01 +01:00
Update import path in go code vmware -> goharbor Signed-off-by: Daniel Jiang <jiangd@vmware.com> 2018-08-23 09:02:20 +02:00			`WORKDIR /go/src/github.com/goharbor/harbor/src/adminserver`
configure harbor 2016-12-30 11:04:01 +01:00
Reduce the output of build. The following are done to avoid travis-ci failing due to too much log size. 1) Update Makefile and scripts to make go build less verbose. 2) Make tdnf less verbose 2018-02-27 08:01:14 +01:00			`RUN go build -a -o /go/bin/harbor_adminserver \`
configure harbor 2016-12-30 11:04:01 +01:00			`&& chmod u+x /go/bin/harbor_adminserver`
Initialise Harbor DB schema in Harbor UI/adminserver container This commit fixes #5040, the harbor-db image will only contain empty databases, and harbor ui container will use migrate tool to run initial SQL scripts to do initialization. This is helpful for the case to configure Harbor against external DB or DBaaS like RDS for HA deployment However, this change will results some confusion as there are two tables to track schema versions have been using alembic for migration, for this release we'll try to use alembic to mock a `migration` table during upgrade so the migrator will be bypassed, in future we'll consider to consolidate to the golang based migrator. Another issue is that the UI and adminserver containers will access DB after start up in different congurations, can't ensure the sequence, so both of them will try to update the schema when started up. 2018-06-27 11:49:46 +02:00
			`COPY ./make/migrations /go/bin/migrations`
configure harbor 2016-12-30 11:04:01 +01:00			`WORKDIR /go/bin/`
			`ENTRYPOINT ["/go/bin/harbor_adminserver"]`