-
Notifications
You must be signed in to change notification settings - Fork 0
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
can't connect to server #1
Comments
Hi Fabrice, |
Hello,
Actually I ran the container via docker desktop using the RUN command...
Fabrice
…-----Message original-----
De: romainGuiet ***@***.***>
à: BIOP ***@***.***>
Cc: fabricesenger ***@***.***>; Author ***@***.***>
Envoyé: lundi 12 février 2024 15:24 CET
Sujet : Re: [BIOP/biop-desktop-doc] can't connect to server (Issue #1)
Hi Fabrice,
I'm sorry it's a silly question but just to clarify, you pulled the image but did you ran it using the command :
docker run -it --rm -p 8888:8888 --gpus device=0 biop/biop-desktop:0.0.7
Cheers,
Romain —
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
From docker desktop, using the Run it opens the window "Run a new container", I still recommend to use a command line like Let me know if it works for you! Cheers, R |
Hello Romain,
I tried first option, trough docker desktop and ,
Second option is still a little bit puzzling to me (i will try to work this out ) as it is not obvious as to how to acces the terminal
Now I have to test the tools ;)
Have a nice day,
Fabrice.
De: "romainGuiet" ***@***.***>
À: "BIOP/biop-desktop-doc" ***@***.***>
Cc: "FABRICE SENGER" ***@***.***>, "Author" ***@***.***>
Envoyé: Mardi 13 Février 2024 08:22:07
Objet: Re: [BIOP/biop-desktop-doc] can't connect to server (Issue #1)
From docker desktop , using the Run [ https://github.com/BIOP/biop-desktop-doc/assets/8309560/e138e864-7308-4175-a2bc-564e15edae6c | image.png (view on web) ] it opens the window "Run a new container",
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/6d5145a2-1d2e-4a30-a8e0-bdf09478fd7c | image.png (view on web) ]
click on "optional settings" , and enter 8888 in the second Host port
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/ab256e6c-bc28-44bc-80a7-75981a2ad844 | image.png (view on web) ]
after clicking RUN, it starts:
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/95ff4e9a-ea63-4f74-a396-165d6a81617d | image.png (view on web) ]
You can now open the [ http://127.0.0.1:8888/lab | http://127.0.0.1:8888/lab ]
I still recommend to use a command line like docker run -it --rm -p 8888:8888 --gpus device=0 biop/biop-desktop:0.0.7 so you can specify the gpu option. (I guess it's do-able in docker desktop too, I just don't know how )
Let me know if it works for you!
Cheers,
R
—
Reply to this email directly, [ #1 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AXWLY5RHQYEAJYRJVJHYPTLYTMIB7AVCNFSM6AAAAABDEU4C5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBQGU3DINRWGQ | unsubscribe ] .
You are receiving this because you authored the thread. Message ID: ***@***.***>
|
aaand it's running
De: "romainGuiet" ***@***.***>
À: "BIOP/biop-desktop-doc" ***@***.***>
Cc: "FABRICE SENGER" ***@***.***>, "Author" ***@***.***>
Envoyé: Mardi 13 Février 2024 08:22:07
Objet: Re: [BIOP/biop-desktop-doc] can't connect to server (Issue #1)
From docker desktop , using the Run [ https://github.com/BIOP/biop-desktop-doc/assets/8309560/e138e864-7308-4175-a2bc-564e15edae6c | image.png (view on web) ] it opens the window "Run a new container",
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/6d5145a2-1d2e-4a30-a8e0-bdf09478fd7c | image.png (view on web) ]
click on "optional settings" , and enter 8888 in the second Host port
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/ab256e6c-bc28-44bc-80a7-75981a2ad844 | image.png (view on web) ]
after clicking RUN, it starts:
[ https://github.com/BIOP/biop-desktop-doc/assets/8309560/95ff4e9a-ea63-4f74-a396-165d6a81617d | image.png (view on web) ]
You can now open the [ http://127.0.0.1:8888/lab | http://127.0.0.1:8888/lab ]
I still recommend to use a command line like docker run -it --rm -p 8888:8888 --gpus device=0 biop/biop-desktop:0.0.7 so you can specify the gpu option. (I guess it's do-able in docker desktop too, I just don't know how )
Let me know if it works for you!
Cheers,
R
—
Reply to this email directly, [ #1 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AXWLY5RHQYEAJYRJVJHYPTLYTMIB7AVCNFSM6AAAAABDEU4C5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBQGU3DINRWGQ | unsubscribe ] .
You are receiving this because you authored the thread. Message ID: ***@***.***>
|
Great ! with the docker desktop or command ?
You can simply ask a windows command prompt and type docker run ... |
Here we go,
now i have to play with the different tools.
Of course i lt you know how it goes,
Best,
Fabrice
De: "romainGuiet" ***@***.***>
À: "BIOP/biop-desktop-doc" ***@***.***>
Cc: "FABRICE SENGER" ***@***.***>, "Author" ***@***.***>
Envoyé: Mercredi 14 Février 2024 14:30:26
Objet: Re: [BIOP/biop-desktop-doc] can't connect to server (Issue #1)
aaand it's running
Great ! Can I ask a screen shot ? 😁
BQ_BEGIN
Second option is still a little bit puzzling to me (i will try to work this out ) as it is not obvious as to how to acces the terminal
BQ_END
You can simply ask a windows command prompt and type docker run ...
—
Reply to this email directly, [ #1 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AXWLY5ROGMGSG7EVEYUKTFTYTS37FAVCNFSM6AAAAABDEU4C5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBTG43TINJQHA | unsubscribe ] .
You are receiving this because you authored the thread. Message ID: ***@***.***>
|
Hello !
Hi there I pulled the container via docker desktop ... now I want to run the dekstop following the instruction for local use, unfortunatly I can't connect to the given adress
Any hints are welcome,
Fabrice.
The text was updated successfully, but these errors were encountered: