This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 472
database initialization problem when using different docker tags? #1639
Labels
Comments
Same problem here, but i did not use |
Today I tried to update an older opensuse/portus:head image (0bf3113a7bed) to 2.3 (5fd3f2196938) and it fails on the exact same issue:
|
mssola
added a commit
to mssola/Portus
that referenced
this issue
Sep 18, 2018
This task should be used when setting up the database instead of the usual combination. This handles databases with pending migrations, new databases, etc. See SUSE#1639 See SUSE#1712 Signed-off-by: Miquel Sabaté Solà <[email protected]>
mssola
added a commit
to openSUSE/docker-containers
that referenced
this issue
Sep 18, 2018
The commit 914cc9ebfdee7b22ee934e6cc4bac0bfd6dfa9fd of Portus introduced the `portus:db:configure` task, which is a replacement for `db:setup` in containerized environments. See SUSE/Portus#1639 See SUSE/Portus#1712 Signed-off-by: Miquel Sabaté Solà <[email protected]>
This has been finally fixed with #1970 and openSUSE/docker-containers@293e289. The Thanks everyone for the feedback 👏 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following the request from @mssola to open a new issue regarding the problems with the db when upgrading portus described in #1620 , i tried to reproduce the problem and i got it, these are the steps:
2.3
tag (image: opensuse/portus 2.3 d47008369714 17 hours ago)2.3
tag for portus and background services, versiondocker-compose down
(persistent volumes)head
tag (image: opensuse/portus head 42b0d1ac54c0 17 hours ago)head
tagit seems that the issue does not occur if you repeat steps using the same image, i'm not sure if we should try with different images version of the same tag (i.e. with the next update of head?).
Notes:
2.3 version was
2.3.0@6c27eb83e3b23b12ce62d39e6823ec8cf5747921
.head version was
2.4.0-dev@46ae80aeed17075974988de5a88a75fd9d4ebb53
.The text was updated successfully, but these errors were encountered: