Contributing guidelines
I've found a bug, and:
Description
When using daemon-config on a Windows runner, the config file gets rendered without any double quotes and so is invalid JSON. The config then gets ignored when the daemon starts so it's quite tricky to tell what's going on.
Example:
with:
daemon-config: |
{
"experimental": true
}
Becomes { experimental: true } in daemon.json.
Expected behaviour
For daemon-config to render valid JSON.
Actual behaviour
Invalid JSON.
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
Docker daemon logs
Additional info
No response
Contributing guidelines
I've found a bug, and:
Description
When using
daemon-configon a Windows runner, the config file gets rendered without any double quotes and so is invalid JSON. The config then gets ignored when the daemon starts so it's quite tricky to tell what's going on.Example:
Becomes
{ experimental: true }indaemon.json.Expected behaviour
For
daemon-configto render valid JSON.Actual behaviour
Invalid JSON.
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
Docker daemon logs
Additional info
No response