-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support custom LogType drivers #783
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
Comments
I can submit a pull request if this approach would be ok |
Or maybe we need switch to String instead enum? enum could still exist as enum of Strings? |
@KostyaSha Wouldn't that break backwards compatibility? Current users using getType() and setType(...) will have compile errors |
It will, but i want soon make 3.1.0 with swarm support. For now i think we can simply add new log type name. |
Great, I did this to solve the problem |
When using the docker rempote api against synology dsm it looks like they have implemented their own log driver named "db"
Currently inspecting a container gives the following exception
Output of synology docker version
Relevant part of
docker inspect
It would be great if this could pass without throwing an exception. A log warning that it's dropped and changed to null would suffice.
There is a comment on Line 26 https://github.com/docker-java/docker-java/blob/master/src/main/java/com/github/dockerjava/api/model/LogConfig.java#L26 about unsupported drivers.
The text was updated successfully, but these errors were encountered: