Skip to content
This repository has been archived by the owner on May 26, 2022. It is now read-only.

Running docker seedDb command not working as expected #103

Open
ed42311 opened this issue Aug 12, 2020 · 2 comments
Open

Running docker seedDb command not working as expected #103

ed42311 opened this issue Aug 12, 2020 · 2 comments
Labels
docker Docker or docker compose

Comments

@ed42311
Copy link
Contributor

ed42311 commented Aug 12, 2020

Original issue #91
From @kimcs

Also the seedDb command for docker at the bottom of the README does not work either, perhaps this is a similar issue?
@ed42311 ed42311 added the bug label Aug 12, 2020
@ed42311
Copy link
Contributor Author

ed42311 commented Aug 12, 2020

Currently What I see occurring:
Screenshot from 2020-08-12 15-25-18

It looks like the services are run but the seedDd command is looking for 4001 and getting kicked out.
@kimcs Let me know if you are running into a similar issue so we can reproduce and diagnose

@ed42311 ed42311 mentioned this issue Aug 12, 2020
Closed
@ed42311
Copy link
Contributor Author

ed42311 commented Aug 12, 2020

this might be relevant: #26

@ed42311 ed42311 added docker Docker or docker compose and removed bug labels Aug 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
docker Docker or docker compose
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ed42311