Skip to content
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

Use DockerHub automated build to provide official docker image #2

Closed
tobegit3hub opened this issue Jun 7, 2016 · 7 comments
Closed

Comments

@tobegit3hub
Copy link

Now we can build the new docker image from Dockerfile in this repo. Is that possible to provide the official one so that we don't need to build by ourselves and just docker pull saiprashanths/dl-docker?

@saiprashanths
Copy link
Collaborator

The CPU build is on Docker Hub (via automated build) and you can get that using docker pull floydhub/dl-docker:cpu.

The automated build for the GPU on Docker Hub is timing out, likely because they have timeout restrictions. I can build locally and push it, but that makes it difficult to keep it up to date with changes in the Dockerfile.gpu. I'll see if I can work around the timeout. Keeping this issue open for now.

@jarrydfillmore
Copy link

Agree!

@tobegit3hub
Copy link
Author

Good job @saiprashanths 👍

It would be great to add the usage of docker pull floydhub/dl-docker:cpu in README.

@saiprashanths
Copy link
Collaborator

I've added docker pull for the cpu version to the README. I'll look into splitting the GPU file into multiple Dockerfiles to see if that helps overcome the timeout issue.

@Kaixhin
Copy link

Kaixhin commented Jun 11, 2016

CUDA builds do indeed tend to trigger timeouts (since the hardware specs are rather minimal too) - I've needed to split builds for Caffe and Torch for example.

A (messy) alternative is to have either kaixhin/cuda-caffe or kaixhin/cuda-torch as your base image. Even then you may still need to split the build though...

@saiprashanths
Copy link
Collaborator

I'm working on splitting the build. First try timed out again. Will try another variation or use your image.

@Kaixhin
Copy link

Kaixhin commented Jun 11, 2016

If you want to squeeze more instructions into your builds, send outputs to /dev/null. I talked to someone at Docker who said that logging actually has a reasonable impact, so this is a valid strategy (although it makes debugging impossible).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants