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

6026 suppress progress when logging level info or debug #6217



None yet
3 participants
Copy link

commented Sep 24, 2018

Resolves #6026

Setting --log-level to WARNING, ERROR or CRITICAL will now hide progress messages.

BEllis added some commits Sep 13, 2018

[#6026] Added -q, --quiet option to 'up' and 'down' commands to suppr…
…ess parallel stream messages.

Signed-off-by: Ben Ellis <>
[#6026] Removed -q options and instead force quiet progress messages …
…if log-level is WARNING or lower.

Signed-off-by: Ben Ellis <>
Merge branch 'master' into 6026-suppress-progress-when-logging-level-…

Signed-off-by: Ben Ellis <>

This comment has been minimized.

Copy link

commented Nov 22, 2018

This PR has been idle for a couple of months now. Any chance of getting it reviewed?


This comment has been minimized.

Copy link

commented Mar 1, 2019

Checking in on this as it'd be nice to have. Is there something preventing this from moving forward?


This comment has been minimized.

Copy link

commented Mar 22, 2019

Yes. I would like to do that as renewing certbot. YOU HAVE TO HAVE ACCESS TO PORT 80/443. So you have to pull down the container, run certbot renew, and bring it up again. Only way as its a security issue. cannot use alternate ports.
And looking into this, best path has been to simply pull it down and renew and start up again during off hours.
Using &> to pipe output to some place can work here, but its not a good path as you cannot detect any output due to error bringin up or down the container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.