-
Notifications
You must be signed in to change notification settings - Fork 16
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
Include the Dockerfiles #6
Comments
Any best practice on how we should we organize/name them? A subdirectory for each tool? Or create .Dockerfile or something? |
I was thinking subdirectory for each tool |
Ok, before I read this I went and put the dockerfiles in subdirectories.. does the current structure make sense? |
subir for each lgtm. Thanks @fredhsu @dave-tucker |
TODO: move to the Gopher-Net docker hub account someone setup. Ty to whoever set it up. |
@nerdalert that was me! We needed that for the OVS plugin. |
Would make a lot of sense to include the Dockerfiles here and to set up autobuilds on the dockerhub. That way, it's easy to remember to pull
gophernet/<tool>
As they are maintained here, we can also make sure they are of good quality and it's a central place where people can open issues etc..
Also, with a bit of magic #4 and #5, we can embed the Dockerfile on the page + explain a little about "how" the tool was Dockerized
The text was updated successfully, but these errors were encountered: