-
Notifications
You must be signed in to change notification settings - Fork 5
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
deepdream-cli-docker hangs in ubuntu 18.04 #4
Comments
This is because you put |
it looks like it's using 100% of 1 of the CPUs. The process does take some time. Can you try a smaller photo/picture? |
thank you for your replies. I am learning still about docker. I resized the image to 400x300 pixels. The command executed to completion in 2 minutes. I thought I was in for another hang since the last lines I saw were:
but then I got the bash prompt back. whew. I appreciate the work you put into the notebook as well. In it, you listed all the layers that the algorithm develops. I modified the script to loop through them all. Some interesting variations. However, some of the layers fail - specifically the ones with the word 'split' at the end but then |
I successfully installed docker community edition and it runs fine. Even added myself as a user so I dont have to type sudo before every docker command. I start with
cat /home/stefan/Pictures/DSC_1789.JPG | docker run -i saturnism/deepdream-cli > output.jpg
and get
.
.
.
.
lots of stuf
.
.
.
.
and then it just hangs there
htop shows this
https://imgur.com/yAkmA7D
Waiting 15' nothing happens
ctrl-C and I get
Interestingly, when I run this
cat /home/stefan/Pictures/DSC_1789.JPG | docker run saturnism/deepdream-cli > output.jpg
(notice the absence of the -i flag) I get this error
and when I run this
cat /home/stefan/Pictures/DSC_1789.JPG | docker run -iterations=1 saturnism/deepdream-cli > output.jpg
(notice -iterations=1 flag)
I get
the input device is not a TTY
running
docker run -i saturnism/deepdream-cli -h
gives
but none of the other flags (-o, -s, -l, --layers) work
The text was updated successfully, but these errors were encountered: