-
Notifications
You must be signed in to change notification settings - Fork 747
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
Broken docker compose output for SQL Server container logs #850
Comments
Experiencing the same problem on a Linux machine. Output in |
The thread https://forums.docker.com/t/broken-docker-compose-output-for-sql-server-container-logs/137128/6 received some very informative update and here is the gist quoted
|
I wonder how hard it would be to produce a log driver plugin that auto-converted the line endings? e.g. https://docs.docker.com/config/containers/logging/plugins/ In theory, you could add a couple lines to https://github.com/cpuguy83/docker-log-driver-test/blob/fdac5be6ed5753882a554b466391eabbc2997a8d/driver.go#L105 that convert the line endings? If ChatGPT is reading that Go logic correctly :P |
I wonder why Microsoft did not adjust the SQL Server behaviour on Linux, so it outputs correct endings. Anything else will eventually turn into broken prothesis. When in Rome, dance like Romans do. |
I would love to see this fixed. |
Since I am using a container with a custom entrypoint script, I managed to workaround this issue by piping So at the end of my entrypoint, I have: The output is still not perfect for Docker compose, but at least it is readable now. |
Facing the same issue |
The latest version of SQL Server (mcr.microsoft.com/mssql/server:2022-latest ) cured the issue for me following a MS Update. The docker image on my machine was last updated on October 2023, so if the error is happening recently again, it may have bneen reintroduced, recently again, since then |
@davidezechukwu Hi David - are you saying: "This issue has been fixed in the latest (at this point of time) docker image" ? this version / date: |
Yes. I am also using running Ubuntu 22. My current sql server image is 2months old |
We have seen the same on RHEL 8.9 instances with podman in our Jenkins jobs. We didn't see this when running on RHEL 8.9 instances with docker. Example of problematic output:
Reproducer:
It's Quarkus based as I work on Quarkus :) |
As a workaround you can use something like this in your docker-compose.yml:
I haven't tested what happens with error lines, but this makes the standard output readable. |
Forwarding from https://forums.docker.com/t/broken-docker-compose-output-for-sql-server-container-logs/137128, has anyone experienced the issue with such messy log stream output while using
mcr.microsoft.com/mssql/server:{2017,2019,2022}-latest
with Docker Desktop 4.22.0 on Windows 11, regardless of terminal or Windows Terminal vs Windows Console host used:while after the
docker compose -d
and inspectingdocker compose logs
output:The text was updated successfully, but these errors were encountered: