Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

migration not worked if DB server existed but project is new #27

Open
prudnitskiy opened this issue May 16, 2019 · 0 comments · Fixed by #39
Open

migration not worked if DB server existed but project is new #27

prudnitskiy opened this issue May 16, 2019 · 0 comments · Fixed by #39

Comments

@prudnitskiy
Copy link

If DB server image is exist but DB wasn't created - migration and run will fail.

Steps to reproduce:

  • create project. DB will be created
  • create another project with the same server (kind/IP). Make will fall on DB create/migrate

Errors. Make run:

+ db
+ run
55a6e918b887d63fe329f2c971954806d8decbbb65a8f8045176b0a6f4d2b249
Using config file: /etc/orinoco/default.conf
2019-05-16T14:58:36.002Z	INFO	orinoco	{"version": "v0.0.0-git-0960f0e-master"}
2019-05-16T14:58:36.166Z	ERROR	sync /dev/stderr: invalid argument; sync /dev/stdout: invalid argument
2019/05/16 14:58:36 Service start error: pq: database "orinoco" does not exist

make migrate-up:

Unable to find image 'prudnitskiy/orinoco:v0.0.0' locally
docker: Error response from daemon: pull access denied for prudnitskiy/orinoco, repository does not exist or may require 'docker login'.
See 'docker run --help'.
Makefile:131: recipe for target 'migrate-up' failed
make: *** [migrate-up] Error 125
@takama takama mentioned this issue Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant