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
I recently cloned this repo on a new macbook and ran into the following error When running make docker-start:
Pulling app (godbledger:latest)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.
Continue with the new image? [yN]y
Pulling app (godbledger:latest)...
ERROR: pull access denied for godbledger, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
After some investigation, it appears that:
docker-compose.yml references the godbledger image
there is no dockerfile in this repo for the godbledger image
I suggest updating the README.md file in this repo with some additional instructions either to run make docker-build in the core repo first or to share this error message and remediation steps in README.md under a new Known Issues section.
The text was updated successfully, but these errors were encountered:
davidalpert
added a commit
to davidalpert/godbledger-web
that referenced
this issue
Apr 13, 2022
this is a prereuqisite of this repo's docker-build target
and must be done seperately since the dockefile for the
server image lives in the core godbledger repo not in
this one.
I recently cloned this repo on a new macbook and ran into the following error When running
make docker-start
:After some investigation, it appears that:
docker-compose.yml
references thegodbledger
imagegodbledger
imageI believe that this repo assumes that the
build-docker
target has been successfully run in the core https://github.com/darcys22/godbledger repo (step 1 from https://github.com/darcys22/godbledger#running-in-docker) before running themake docker-start
target in this repo.I suggest updating the
README.md
file in this repo with some additional instructions either to runmake docker-build
in the core repo first or to share this error message and remediation steps inREADME.md
under a new Known Issues section.The text was updated successfully, but these errors were encountered: