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
Describe the bug
When I use the logging configuration for my compose service with the driver option set to "none", then I get a fatal error and am unable to start my compose service.
Steps to reproduce
Given the following compose service definition inside docker-compose.yaml:
I have looked into the gap and found this would require an upstream change to nerdctl. I have asked maintainers to consider this use case for containerd/nerdctl#1039.
@coderbirju that's great news. Any idea when nerdctl 2.0 will be supported by Finch? I tried using logging driver "none" with Finch version v1.4.3 released recently and it doesn't appear to use nerdctl 2.0 as I still got the same output as reported initially.
Describe the bug
When I use the logging configuration for my compose service with the
driver
option set to"none"
, then I get a fatal error and am unable to start my compose service.Steps to reproduce
Given the following compose service definition inside
docker-compose.yaml
:When I run
finch compose up elasticsearch
I get the following output:I also tried to use the
logging
configuration with thedriver: "none"
option for a different service and got the same result.Expected behavior
I expected the
elasticsearch
service to start successfully.Screenshots or logs
N/A
Additional context
finch-support-20231031104304.zip
The text was updated successfully, but these errors were encountered: