-
Notifications
You must be signed in to change notification settings - Fork 9
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
Errorred running docker pull shuzhao/asari #20
Comments
Solutionuse specific asari version based tag instead:
|
amnahsiddiqa
changed the title
Errorred ruling docker pull shuzhao/asari
Errorred running docker pull shuzhao/asari
Jul 21, 2022
Is the Asari under development? @amnahsiddiqa
I will also try docker now. |
@gmhhope No. I can tell more if I know more details of your system etc (its organizational/personal what macOS ); also just FYI I just installed it right now and there is no problem on my end. Docker is best to use. |
Also the error sounds to me like you were using a virtual environment? |
Yes, docker is running fine.
Thanks!
…On Fri, Jul 22, 2022 at 7:00 AM Amnah Siddiqa ***@***.***> wrote:
Also the error sounds to me like you were using a virtual environment?
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADDBUIPUC3QTRPW7UYUR26TVVJ5NPANCNFSM54IUUJPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes sounds like MG deleted his venv.
…On Fri, Jul 22, 2022 at 7:00 AM Amnah Siddiqa ***@***.***> wrote:
Also the error sounds to me like you were using a virtual environment?
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGHKF3D67P5HA5CVRIXOKLVVJ5NPANCNFSM54IUUJPQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using default tag (latest) would return error:
The text was updated successfully, but these errors were encountered: