I can download private Docker images with this build (yay!), and I also tested the search and slash bugs reported by others and this build does indeed fix them.
However, I'm also having a weird problem I've never seen before. It's entirely reproducible, and given it breaks the scripts we use at work, I'm fairly certain it's not present in the Docker.com-packaged docker-engine-1.9.1-1.fc23.x86_64 (which is what I'm using while waiting for a fix).
If I do "docker pull containerA", I have to wait a few seconds before I can successfully "docker-compose run containerB bash". If I don't wait long enough (sometimes less than a second, sometimes more), I get an error like:
Cannot start container f1351f0d3025f8140d9f0e90a2b0bb17e427ca2bb5d6f3264289144cd329ff77: [8] System error: operation not permitted
BZ#1287206 Cannot download private images with new version of Docker
BZ#1287049 Docker search does not work on default settings.
This update has been submitted for testing by miminar.
I was sure it is fixed. #1287049
I can download private Docker images with this build (yay!), and I also tested the search and slash bugs reported by others and this build does indeed fix them.
However, I'm also having a weird problem I've never seen before. It's entirely reproducible, and given it breaks the scripts we use at work, I'm fairly certain it's not present in the Docker.com-packaged docker-engine-1.9.1-1.fc23.x86_64 (which is what I'm using while waiting for a fix).
If I do "docker pull containerA", I have to wait a few seconds before I can successfully "docker-compose run containerB bash". If I don't wait long enough (sometimes less than a second, sometimes more), I get an error like:
Cannot start container f1351f0d3025f8140d9f0e90a2b0bb17e427ca2bb5d6f3264289144cd329ff77: [8] System error: operation not permitted
Beland this seems like a different issue.
Works for me.
Works for me.
Missed a checkbox. Sigh.
This update has been pushed to testing.
works for me.(forgot checkbox...)
I have installed this. It has fixed the issue of the leading forward-slash (/) when commiting snapshots.
Thank you for your efforts <3
Fixed the leading slash for me.
This update has been submitted for stable by bodhi.
Works for me
Works for me.
If you had any images prefixed with a / those had to be deleted by their image ID...
Forks for me.
This update has been pushed to stable.
Works for me
karma: +1