-
Notifications
You must be signed in to change notification settings - Fork 797
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
Docker build logs unreadable #1881
Comments
It is the docker build output. Does it happen for all builds a particular image? Can you try a simply build like this:
This should generate some output in your logs and it should be perfectly normal. |
I used method 4. The build logs:
This is normal as you said. Is there a way we can fix this? I fixed this temporarily using Hence the issue #1883. |
So looks like your container's build process is somehow throwing some garbage character into the logs.... It's apparently specific to your build. If you can share a sample Dockerfile that reproduces the issue, I can look into that. |
It's a rust build. I cannot share unfortunately. Anyway I found a workaround. Thank you very much (for now). |
I'm on caprover
v1.11.0
and I'm using this CLI command:caprover deploy --caproverUrl https://captain.domain --caproverApp appName --tarFile tarName
It works but the Docker build logs are like the below both in my console and on captain's app's dashboard "Deployment" tab:
and so on...
It's unreadable to say the least.
Why?
Is the Docker logs system?
Can we use the
--progress plain
argument on thedocker build
command? How?The text was updated successfully, but these errors were encountered: