Skip to content
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

console output during build #526

Closed
graingert opened this issue Jul 20, 2018 · 5 comments
Closed

console output during build #526

graingert opened this issue Jul 20, 2018 · 5 comments

Comments

@graingert
Copy link

I'd like to be able to see the console output eg of compilations/package manager installs so I get some idea of build status

@graingert
Copy link
Author

or if a build fails I'd like to see the logs to debug

@tonistiigi
Copy link
Member

Currently, you get the logs with --no-progress or when invoked without a terminal. We are thinking of a best way to show logs on the terminal output. If you have suggestions, let the know.

or if a build fails I'd like to see the logs to debug

This should be the case already.

@sudo-bmitch
Copy link

I'm thinking of two potential output flags.

  1. Classic output that mirrors the current build output style as closely as possible to help with those that already have scripting or processes built around that output.

  2. Verbose output that just shows the output after each step completes. Same as it does now for errors, but also do it for successful steps.

Instead of the --console boolean flag, perhaps a --output [console|terminal|verbose|classic] flag?

@tonistiigi
Copy link
Member

@sudo-bmitch see #504

@AkihiroSuda
Copy link
Member

I suppose this is closable now (buildctl build --progress=plain)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants