-
Notifications
You must be signed in to change notification settings - Fork 20
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
No start_daemon in the Docker cli? #9
Comments
It worked! Just took a really long time to finish (>1 hour) even though I already had downloaded the image for 3.3. I saw that when I did not specify the image, it used 3.2 by default. I wonder if it could be trying to use that image instead for some step... but anyway, feel free to ignore this part, but the |
When did you downloaded the image? Was it today or last week? |
First thing in the morning, before joining the Zoom meeting. |
Today I am using my personal laptop, which is ~10 years older than BSC's, and normally slower. But the I can see the container has been up and running for some time already. (pycompss) kinow@ranma:~$ docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
compss/compss-tutorial 3.3 c7299b31198c 3 days ago 3.1GB
...
kinow@ranma:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8318db7a39ef compss/compss-tutorial:3.3 "/usr/sbin/sshd -D" About an hour ago Up About an hour 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 22/tcp, 43000-44000/tcp, 0.0.0.0:8888->8888/tcp, :::8888->8888/tcp pycompss-master-docker-tutorial I launched And I can see that the local ports/sockets were bound too: kinow@ranma:~$ netstat -tlnp | grep -E "8888|8080"
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN -
tcp6 0 0 :::8888 :::* LISTEN -
tcp6 0 0 :::8080 :::* LISTEN Still, opening The container doesn't seem to have anything in its stdout for logs? kinow@ranma:~$ docker logs 8318db7a39ef
kinow@ranma:~$ And opening a terminal in the container created by the pycompss-cli, it looks like there are no jupyter nor monitor running. And some weird files inside the root of the container as well. kinow@ranma:~$ docker exec -ti 8318db7a39ef /bin/bash
root@8318db7a39ef:/# netstat -tlnp
bash: netstat: command not found
root@8318db7a39ef:/# ps
PID TTY TIME CMD
65 pts/0 00:00:00 bash
75 pts/0 00:00:00 ps
root@8318db7a39ef:/# ls
'=0.24.2' '=1.3.0' dev lib32 mnt resources.xml srv var
'=0.8.0' '=2.2.3' etc lib64 opt root sys
'=1.0.2' bin home libx32 proc run tmp
'=1.1.5' boot lib media project.xml sbin usr
root@8318db7a39ef:/# And the Jupyter command fails: (pycompss) kinow@ranma:~$ pycompss jupyter
Traceback (most recent call last):
File "/home/kinow/mambaforge/envs/pycompss/bin/pycompss", line 8, in <module>
sys.exit(main())
File "/home/kinow/mambaforge/envs/pycompss/lib/python3.10/site-packages/pycompss_cli/cli/pycompss.py", line 45, in main
ActionsDispatcher().run_action(arguments)
File "/home/kinow/mambaforge/envs/pycompss/lib/python3.10/site-packages/pycompss_cli/core/actions_dispatcher.py", line 53, in run_action
action_func()
File "/home/kinow/mambaforge/envs/pycompss/lib/python3.10/site-packages/pycompss_cli/core/local/actions.py", line 111, in jupyter
if jupyter_args[0] == 'lab':
IndexError: list index out of range |
Level
MINOR
Component
PYTHON BINDING
compss/builders/specs/cli/PyCOMPSsCLIResources/pycompss_cli/core/docker/cmd.py
Line 230 in 172d245
Environment
3.3.2
python
$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS" $ pip list Package Version ------------------ ---------- certifi 2023.11.17 charset-normalizer 3.3.2 docker 7.0.0 idna 3.6 packaging 23.2 pip 23.3.2 pycompss-cli 3.3.2 requests 2.31.0 setuptools 69.0.3 urllib3 2.1.0 wheel 0.42.0
Description
For some strange reason the pycompss init command fails for me. I already have the compss-tutorial image 3.3. But when I launch it, it still stays open for a very long time.
So I decided to try a few things to see if I could get it to work, and at one point I think that made the code reach a function that calls
start_daemon
for Docker, but fails as that function does not exist on thedocker/cli.py
DockerCmd
object (and the parent ofDockerCmd
isobject
, and I couldn't find any metaclass or something else that would define that function).Minimal example to reproduce
pycompss-cli
installedFor me, this stays running forever. I had already downloaded
compss/compss-tutorial:3.3
, so not sure what it is doing (htop
andps
didn't help, might strace it later if I don't find any other solution). But it does create the env, in another terminal:Then if I change to
test
,And try to start the monitor:
Exception
AttributeError: 'DockerCmd' object has no attribute 'start_daemon'
Expected behaviour
The daemon is launched, I think.
The text was updated successfully, but these errors were encountered: