Closed wrenchpilot closed 5 years ago
Was able to get past this by editing the docker-compose.yml file and changing the image from: image: 'myos:${TAG:-latest}'
to
image: 'rylandg/myos'
Awesome feedback. Definitely an issue. Short term I will simply put out a patch that relies on the remote image.
Awesome project, if I catch a break I'll see if I can submit some pulls for other editors etc 🙏
Would definitely appreciate it. I prefer code reviews always, when possible. If you have a moment, check this out https://github.com/rylandg/myos/pull/9. If you check it real quick, i'll merge it in a few.
No feedback/error when repo is missing myos create foo does not return an error or fail if the repo is missing. It just runs forever. Running docker-compose up -d by hand returns:
Pulling myos (myos: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 myos (myos:latest)... ERROR: pull access denied for myos, repository does not exist or may require 'docker login'
To Reproduce Steps to reproduce the behavior:
Host OS (please complete if relevant):