Skip to content

Adding Dockerfiles for generating docker images #1145

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

Merged
merged 4 commits into from
Mar 24, 2015
Merged

Adding Dockerfiles for generating docker images #1145

merged 4 commits into from
Mar 24, 2015

Conversation

jbeezley
Copy link
Contributor

For some information, see the README I included. Docker hub has a system for autogenerating builds from github pushes, but it isn't working here due to some cryptic timeout error. I assume the VM it builds on doesn't have enough memory or disk space. For now, we will have to update images manually from time to time (ideally with every push to master).

@aashish24
Copy link
Contributor

This is awesome @jbeezley this is really cool. thanks for pushing it. @williams13 this will make it really easy to access uvcdat (via docker). So no need to build! if not needed

@williams13
Copy link
Contributor

Would like to see this demonstrated.

From: Aashish Chaudhary <notifications@github.commailto:notifications@github.com>
Reply-To: UV-CDAT/uvcdat <reply@reply.github.commailto:reply@reply.github.com>
Date: Saturday, March 14, 2015 at 5:56 AM
To: UV-CDAT/uvcdat <uvcdat@noreply.github.commailto:uvcdat@noreply.github.com>
Cc: Dean Williams <williams13@llnl.govmailto:williams13@llnl.gov>
Subject: Re: [uvcdat] Adding Dockerfiles for generating docker images (#1145)

This is awesome @jbeezleyhttps://github.com/jbeezley this is really cool. thanks for pushing it. @williams13https://github.com/williams13 this will make it really easy to access uvcdat (via docker). So no need to build!


Reply to this email directly or view it on GitHubhttps://github.com//pull/1145#issuecomment-80497093.

@doutriaux1
Copy link
Contributor

seems to have certificate issues, so it might not be great for national labs:

doutriaux1@maryam:[~]:[6382]> docker run -i -t uvcdat/uvcdat ipython
Unable to find image 'uvcdat/uvcdat:latest' locally
Pulling repository uvcdat/uvcdat
93928052b6db: Error pulling image (latest) from uvcdat/uvcdat, endpoint: https://registry-1.docker.io/v1/, Get https://registry-1.docker.io/v1/images/93928052b693928052b6db: Error pulling image (latest) from uvcdat/uvcdat, Get https://registry-1.docker.io/v1/images/93928052b6dbdbf29f399af36bb81153ff1047c78f26707088f0b9FATA[0004] Error pulling image (latest) from uvcdat/uvcdat, Get https://registry-1.docker.io/v1/images/93928052b6dbdbf29f399af36bb81153ff1047c78f26707088f0b9ab40a6dbdf/ancestry: x509: certificate signed by unknown authority 

@doutriaux1
Copy link
Contributor

@jbeezley @aashish24 did I miss something, even w/o firewall I now get:

doutriaux1@maryam:[~]:[6383]> docker run -i -t uvcdat/uvcdat ipython
Unable to find image 'uvcdat/uvcdat:latest' locally
Pulling repository uvcdat/uvcdat
FATA[0040] Get https://index.docker.io/v1/repositories/uvcdat/uvcdat/images: dial tcp: lookup index.docker.io on 128.115.54.1:53: read udp 128.115.54.1:53: i/o timeout 

@jbeezley
Copy link
Contributor Author

I haven't seen that before. A google search seems to indicate that upgrading and/or restarting boot2docker may help. You should have version 1.5. I would try this just to be sure:

boot2docker upgrade
boot2docker restart

mattben added a commit that referenced this pull request Mar 24, 2015
Adding Docker - Adding Dockerfiles for generating docker images
@mattben mattben merged commit fbe51f1 into master Mar 24, 2015
@aashish24 aashish24 deleted the docker branch March 25, 2015 17:17
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

Successfully merging this pull request may close these issues.

5 participants