You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
We have a CD pipeline that uses dynamic build slaves. We recently updated our Docker version to 17.06.0-ce, and noticed that the first run start up s3mock:latest takes much longer (~8--15s) than any subsequent starts (~2s). The start up time continues to be quick, even after I stop, remove, and docker system prune -a all containers. s3mock logs don't show anything noteworthy.
Obviously start up times differ based on what's running docker, but I just wanted to see if you or anyone else noticed similar behavior. The delta between our new slaves, and old ones, really is minimal, and the docker version bump the main difference. Previous slaves didn't exhibit the same behavior. I don't think it's something wrong with this image, but just opening the issue in case others have observed the same so that we can discuss.
Greetings,
We have a CD pipeline that uses dynamic build slaves. We recently updated our Docker version to 17.06.0-ce, and noticed that the first run start up
s3mock:latest
takes much longer (~8--15s) than any subsequent starts (~2s). The start up time continues to be quick, even after I stop, remove, anddocker system prune -a
all containers.s3mock
logs don't show anything noteworthy.Obviously start up times differ based on what's running docker, but I just wanted to see if you or anyone else noticed similar behavior. The delta between our new slaves, and old ones, really is minimal, and the docker version bump the main difference. Previous slaves didn't exhibit the same behavior. I don't think it's something wrong with this image, but just opening the issue in case others have observed the same so that we can discuss.
Thanks!
Slave details:
The text was updated successfully, but these errors were encountered: