-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add Dockerfile #163
Add Dockerfile #163
Conversation
Thanks for pointing to gometalinter issue in scripts directory. I will send PR to address that issue. |
Please move the Dockerfile to extras directory. May be with name |
Hi, how to run this container to make it work with a Gluster cluster? I asked in #73 but now I see you created your own image, but the issue remains unresolved. By the way, this Dockerfile doesn't build, I'm getting this:
|
I am unable to reproduce this on the latest code, and it's odd that it would allow adding/updating the repo but bail on the actual package repo. Is it consistent? If not, it might be related to https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1111882, if so, you may want to double check your network's setting, Edit: also, you can ignore your cached images by adding the |
Maybe I was building the image in a wrong context. I will check it once it's merged. Thanks :) |
That PR only adds documentation, it doesn't change anything about the build itself. |
Ah, sorry, you're right xD |
Uses Debian in order to align build and run images on the same supported platform. Note that
GLUSTER_VERSION
must be set to a number rather than LATEST due to http://download.gluster.org/pub/gluster/glusterfs/LATEST/rsa.pub being a 404 as well as differences in directory structure.I also noticed that despite 567cf6d removing gometalinter, the
scripts/
directory was never touched, so it's still required to be installed for the make commands to work.