-
Notifications
You must be signed in to change notification settings - Fork 114
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
Wrong placement of flag in command #72
Labels
Comments
Thanks for reporting this! Do you want to create a PR to fix it? |
@rndmh3ro yes |
How could I do this? |
nnickie23
added a commit
to nnickie23/cis-docker-benchmark
that referenced
this issue
Dec 2, 2021
Fix the placement of "--no-trunc" flag of docker command
nnickie23
added a commit
to nnickie23/cis-docker-benchmark
that referenced
this issue
Dec 3, 2021
Fix the placement of "--no-trunc" flag of docker command Signed-off-by: nnickie23 <[email protected]>
schurzi
added a commit
that referenced
this issue
Feb 25, 2023
* Fix command flag (#72) Fix the placement of "--no-trunc" flag of docker command Signed-off-by: nnickie23 <[email protected]> * use order defined in documentation Signed-off-by: Martin Schurz <[email protected]> --------- Signed-off-by: nnickie23 <[email protected]> Signed-off-by: Martin Schurz <[email protected]> Co-authored-by: schurzi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
controls/container_images.rb
usesdocker history
to inspect commands, and the command looks like this:Expected behavior
The output without error is expected. This can be achieved by placing the flag
---no-trunc
at the end of command string:Actual behavior
The stdout of running this command is empty because the command has an error:
Example code
OS / Environment
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
Inspec Version
Baseline Version
The text was updated successfully, but these errors were encountered: