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

Errors are not printing out correctly in cnspec #68

Open
tas50 opened this issue Oct 10, 2022 · 1 comment
Open

Errors are not printing out correctly in cnspec #68

tas50 opened this issue Oct 10, 2022 · 1 comment

Comments

@tas50
Copy link
Member

tas50 commented Oct 10, 2022

Describe the bug
When scanning a docker image I hit an error in cnspec that printed to the screen with \n and \t printed instead of being interpreted. The same error printed out correctly in mondoo client.

To Reproduce
Steps to reproduce the behavior:

  1. Run cnspec scan docker image openjdk:18.0-nanoserver --incognito
  2. See error

Expected behavior
\n and \t are interpreted to format the error message correctly.

Screenshots
image

Desktop (please complete the following information):

  • OS: macOS
  • Browser: N/A
  • Version: N/A

Additional context
Nope

@tas50
Copy link
Member Author

tas50 commented Oct 17, 2022

Update on this issue. Now things silently fail:

→ loaded configuration from /Users/tsmith/.config/mondoo/mondoo.yml using source default
→ using service account credentials
→ discover related assets for 1 asset(s)
→ resolved assets resolved-assets=1
→ connecting to asset index.docker.io/library/openjdk@sha256:7e033f2236c1f593bdbbec0b9a0489c13bbc8aa12fad458e0bb4434bdcd1aa98 (container-image)

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

1 participant