You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner. It is now read-only.
During testing, it's possible to have containers run for the first time, but to use db volume contents that mean the DB has already been created. (This will be possible in the real world, too.)
In the event that the database already has a schema created, the schema creation should be skipped.
The text was updated successfully, but these errors were encountered:
in which step do you check if mariadb have the users created, because I saw in the last commit 650e808 , the step that check if database have user/password for database are ready was removed. Now only check if mariadb is up an running but did not check if mariadb have users and databases creates , example (registry database with the correct user). One posible error can appear if mariadb start first comanage but user is not created at time that commonage make any connection trying to use the user that need to connect mariadb.
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
During testing, it's possible to have containers run for the first time, but to use db volume contents that mean the DB has already been created. (This will be possible in the real world, too.)
In the event that the database already has a schema created, the schema creation should be skipped.
The text was updated successfully, but these errors were encountered: