3 ms·

In other news, the issues list [0] just keeps growing by the day, apparently with few or no devs committed to ensuring show-stopping kernel interoperability bug

by sshykes 12y ago

In other news, the issues list [0] just keeps growing by the day, apparently with few or no devs committed to ensuring show-stopping kernel interoperability bugs [1] get resolved in a timely manner. I want to love you docker, but the experience of using your products is often sooo painful! [0] https://github.com/docker/docker/issues https://github.com/docker/docker/issues [1] https://github.com/docker/docker/issues/4036 https://github.com/docker/docker/issues/4036 Karma-wise I'm sure there will be hell to pay for my impolite outburst.. Sorry for the offense! Just calling it like I see it.

shykes 12y ago
You are right that devicemapper (basically lvm snapshots for storage, used as an alternative to aufs/btrfs on many distros including Red Hat) has been a source of headaches for us. It is relatively obscure (we knew we were in trouble when googling libdevmapper error messages returned our own source code as the first result) and frankly not pleasant to work with. But, the good news is that we have made progress recently. In fact the 1.5 release includes several improvements to devicemapper. And as of last week, Red Hat has volunteered a dedicated engineer to escalate devicemapper problems. So, fingers crossed things will be even better in the next release :) Another alternative is to switch storage drivers: aufs and btrfs are popular options.
- sshykes 12y ago
  Thanks for following up Solomon! I'm glad you are at least aware of what is going on with this.
jacques_chester 12y ago
Wider exposure means more issues logged, including dupes and wish lists.
omni 12y ago
GitHub has a really great Pulse feature which gives you a quick look at the flow of PRs and issues in and out of a project: https://github.com/docker/docker/pulse/monthly https://github.com/docker/docker/pulse/monthly Docker has actually been closing issues much more quickly than they come in. Yes, there is a backlog, but that's to be expected from a new project getting a lot of usage. They definitely do not seem to be slouching, though.

by sshykes 12y ago

shykes 12y ago

You are right that devicemapper (basically lvm snapshots for storage, used as an alternative to aufs/btrfs on many distros including Red Hat) has been a source of headaches for us. It is relatively obscure (we knew we were in trouble when googling libdevmapper error messages returned our own source code as the first result) and frankly not pleasant to work with. But, the good news is that we have made progress recently. In fact the 1.5 release includes several improvements to devicemapper. And as of last week, Red Hat has volunteered a dedicated engineer to escalate devicemapper problems. So, fingers crossed things will be even better in the next release :) Another alternative is to switch storage drivers: aufs and btrfs are popular options.

sshykes 12y ago
Thanks for following up Solomon! I'm glad you are at least aware of what is going on with this.

jacques_chester 12y ago

Wider exposure means more issues logged, including dupes and wish lists.

omni 12y ago

GitHub has a really great Pulse feature which gives you a quick look at the flow of PRs and issues in and out of a project: https://github.com/docker/docker/pulse/monthly https://github.com/docker/docker/pulse/monthly Docker has actually been closing issues much more quickly than they come in. Yes, there is a backlog, but that's to be expected from a new project getting a lot of usage. They definitely do not seem to be slouching, though.