-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce number of log messages for Docker pull #24
Comments
addressed with 1513d6e |
The current fix does only work for images that are pulled before an experiment starts. |
MichaelRoeder
added a commit
that referenced
this issue
Feb 28, 2018
Developed version 2.0.0 of the platform. Moved to Docker swarm (using Docker services instead of docker-compose) (#100, #158, makes #24 obsolete). Updated VOS version and made sure that future updates of the version can be done easily (#48). Added cluster health checks (#97). Added support for gathering statistics about the usage of resources (#98). Added the visualization of complex data as diagrams (#125). Cleaned up deployment process (#162).
Can be solved by solving #274 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
When the platform pulls images, it uses the default logging of the Docker client library. However, this behaves similar to the output of Docker and shows the current status of the downlod:
This becomes a problem especially on a Docker swarm cluster where every node generates this huge amount of log messages.
Proposed solution
Create a small class implementing the
com.spotify.docker.client.ProgressHandler
interface and log only those messages, that we are interested in:Use this class when pulling images https://github.com/hobbit-project/platform/blob/master/platform-controller/src/main/java/org/hobbit/controller/docker/ContainerManagerImpl.java#L216
The text was updated successfully, but these errors were encountered: