Replies: 7 comments 3 replies
-
Probably because container was not run: This command |
Beta Was this translation helpful? Give feedback.
-
Hm... Warning message should be improved. Here is just no logs for container, but not because of empty filter. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the information. I am going to resolve this. The logging behavior is Docker related. Thanks! |
Beta Was this translation helpful? Give feedback.
-
@tamarahenson, No, this is portainer related: Portainer should not blame filter, when there is no log messages. |
Beta Was this translation helpful? Give feedback.
-
We have replaced the log viewer since this was last updated - can you confirm whether this is still an issue? |
Beta Was this translation helpful? Give feedback.
-
any update from this issue? i used 2.19.5 and got same issue when running docker-compose for mosquitto
in portainer, container started with same log issue |
Beta Was this translation helpful? Give feedback.
-
Bug description
But nothing is entered into filter field ...
Expected behavior
List of log lines.
Portainer Logs
Click button to view container logs.
Steps to reproduce the issue:
I notice this after server reboot.
Technical details:
**Err.. Is it possible to link other PR where I already have filled in standard questions?
Beta Was this translation helpful? Give feedback.
All reactions