-
-
Notifications
You must be signed in to change notification settings - Fork 22
Unable to start SGE workers via docker-compose on Windows 8.1 #64
Comments
Sure. I think this is ok here (especially since it's our docker-compose setup :). Could you please try the following SGE command to see what happens?
|
Doesn't seem to give any output: Dev@az MINGW64 /dask-drmaa ((cc20f43...))
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
efa6eebce34a daskdrmaa_slave-one "bash /run-slave.sh" 2 hours ago
Up 2 hours slave_one
9fae83c48356 daskdrmaa_slave-two "bash /run-slave.sh" 2 hours ago
Up 2 hours slave_two
b13940296988 daskdrmaa_master "bash -x /run-master" 2 hours ago
Up About a minute 6444-6446/tcp, 8000/tcp sge_master
Dev@az MINGW64 /dask-drmaa ((cc20f43...))
$ docker exec -it sge_master /bin/bash -cx "qstat -f"
+ qstat -f
# No output |
Hmm...that suggests the containers are not being connected for some reason. As contrast, this is what I see when running the same command.
Is anything else trying to use the ports allocated to those Docker containers on your machine? Also not sure how you are running Docker. Recall having various issues when using Docker Machine on VPN for instance. Would expect Docker for Windows to avoid many of these issues. |
I am using Docker Toolbox (for Windows pre-10). No VPN, and those ports should be free. I ran $ docker exec -it sge_master /bin/bash -cx "qhost"
+ qhost
HOSTNAME ARCH NCPU LOAD MEMTOT MEMUSE SWAPTO SWAPUS
-------------------------------------------------------------------------------
global - - - - - - -
slave_one lx26-amd64 1 0.36 995.8M 282.1M 1.1G 8.6M
slave_two lx26-amd64 1 0.36 995.8M 282.1M 1.1G 8.6M However, when I try to run the unit tests, they encounter an error when they try to submit a DRMAA job:
And
Maybe there's some configuration step that I need to run again? |
So are you using Virtual Box then or a different VM? |
Yes, using VirtualBox. |
I'm able trouble reproducing the unit tests based on the given instructions, for Windows. I've done the following:
*.sh
files in the top-level directory of this project.docker-compose build --no-cache
When I run
./start-sge.sh
I see the outputWaiting for SGE slots to become available
after an indefinite amount of waiting:Unfortunately I have no familiarity with SGE. Any suggestions as to how I can debug/fix this? Apologies if this is not appropriate for this issue tracker.
The text was updated successfully, but these errors were encountered: