Replies: 2 comments
-
Confirmed this by setting the daemon to use the json-file logging driver and we show |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ahh so I think we could make a change to the logging driver section in service details to make it more intuitive. If the logging driver is changed in the daemon, whatever it is set to will be the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
EDIT: Changed to a feature request as the original report is not a bug.
Is your feature request related to a problem? Please describe.
If the logging driver is changed in the daemon, in service details it will always show as
Default logging driver
(this applies to all drivers).Describe the solution you'd like
We should pre-fill with whatever the default driver is rather than saying
Default logging driver
Bug description
I have a Swarm created with Docker For AWS, with the daemon configured to use the awslogs log driver.
When I deploy a stack from the CLI, the services use the awslogs driver as well (the one specified at the daemon level) as no log driver as been specified in the docker-stack.yml at the service level.
From Portainer, the service log driver should specify awslogs but it shows "default logging driver" instead.
Expected behavior
Service details panel should display the log driver specified at the daemon level if no additional one has been specified at the service level.
Steps to reproduce the issue:
Technical details:
Beta Was this translation helpful? Give feedback.
All reactions