* bump up version to 1.10.19
upgrade golang to 1.22.5
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: add golang Dockerfile to build goharbor/golang image
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* change "go get" to "go install" as it requires in golang:1.22
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: go install golint
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: update go version in build-package.yml
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: upgrade golang to 1.22.5 to build clair and clair-adapter
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: resolve the permission denied issue
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* debug: remove DNS setting for docker v20
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix "groupadd: group 'postgres' already exists" error when building db base
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* bump up to photon:5.0 mainly to resolve /lib/libc.so.6: version `GLIBC_2.34' not found
use mariadb-18.2.6.tgz as the old one is 404
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: use goharbor/golang 1.21.12
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: update golang version in echo log message when building clair binary and clair adapter
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
* fix: update chart files URL due to 404
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
---------
Signed-off-by: Shengwen Yu <yshengwen@vmware.com>
Make necessary change to make things work with photon 2.0 docker image.
Remove distro-sync to mitigate the build issue and add `--pull` to docker build
command to make sure the latest photon:2.0 will be pulled during build process.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>
The migrate tool will try to create table schema_migration upon opening
the connection to DB. This will cause error when there are multiple
instance of adminserver trying to access the migrator upon start.
This commit move the creation of the table during the initialization of
the DB container.
Signed-off-by: Daniel Jiang <jiangd@vmware.com>
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.
This commit is to enable data migrator to support migrates data
from mysql to pgsql, this is a specific step for user to upgrade
harbor across v1.5.0, as we have move harbor DB to pgsql from
1.5.0. It supports both harbor and notary db data migration,
and be split into two steps with dependency.
It also fix issue #4847, add build DB migrator in make process.
We have to add the uuid/id mapping as new job service will only store uuid.
Further work is in feature branch for now, commit this change to
accelerate migration work.
