Created attachment 377960 [details] emerge --info I upgrade my copy of docker from version 0.9 to 0.11, and when attempting to restart docker I received the error message: Could not locate dockerinit: This usually means docker was built incorrectly. See http://docs.docker.io/en/latest/contributing/devenvironment for official build instructions. However, running strace on docker shows that is in fact finding dockerinit, it just rejects the executable for some reason. Further Googling revealed: https://github.com/dotcloud/docker/issues/3826 , which mentioned binary stripping could cause issues. On a chance, I tried emerging docker with FEATURES=-installsources (my system has installsources by default), which allowed docker to successfully build and start. It seems to be running properly now.
This was reported on the overlay at https://github.com/tianon/docker-overlay/issues/18, and we decided to wait to push the fix into portage until upstream has a new release (which will probably be next week or very shortly thereafter). Is this serious enough that we ought to do a new -r1 sooner than that with the fix?
Personally, I don't think it is too much of an issue. The workaround is simple, and if updated ebuilds are available in the overlay then people can easily use them. And this release of docker is still keyworded, so it won't hit stable users. Maybe if you just mark this bug as confirmed, so anyone else who hits this issue knows it's being worked on, and sees that the fix is inbound?
I agree, that would be an excellent idea. I'm only allowed to mark as resolved, so if anyone else is reading this and has permission to mark it as confirmed (even as the assignee, which is weird), please feel free to do so for us. :)
This was fixed in tree in 1.0.0 (and also the newly uploaded 1.0.1). :)
