[meta] define a set of fixes necessary for a Deis v1 LTS release #4776
Comments
I would ❤️ if #4554 could get manual testing and be included. I know its a bear but it feels like its either time to manually test it finally or just close it. |
Hello guys. Thank you for your work. Deis is actually great. We use it in production in 1 DC and planning up +2 production clusters in 2 other DC's in February 2016. |
Thank you @rvadim!! |
#4494 would need to be fixed as well. Running a coreos/deis install entirely behind a corporate proxy makes this a showstopper. Actually, docker 1.9 supports build-args to be propagated to built images: This might be an easy way to globally set and propagate to all deis containers. That, and making sure that the docker-in-docker builder also passes it to the herokuish container. |
#4787 might be beneficial. |
Thanks for deis guys, deis is really nice product. |
A way to get around this moby/moby#14788 |
#4763 : "tags:set isn't restricting my app to certain hosts" |
@dmcnaught yes, that's been merged in master so it will go into the LTS release. |
#4732 or getting docker to cleanup its iptables in some way or another. |
can someone please look at #3479? |
The next minor release of Deis is intended to be a "long-term support" release that provides a stable, supported platform that will continue to receive fixes for many months.
Please help us ensure that Deis LTS will meet your needs by pointing out which changes are necessary for your use. Add a comment here referencing an existing GitHub issue or describing the problem, and we will roll them up into an "LTS" milestone and update the roadmap document so we can all track progress.
The text was updated successfully, but these errors were encountered: