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

[Bug] 1.1.5 doesn't take into account a changed data-root #568

Open
OdinVex opened this issue Feb 2, 2025 · 2 comments
Open

[Bug] 1.1.5 doesn't take into account a changed data-root #568

OdinVex opened this issue Feb 2, 2025 · 2 comments
Assignees

Comments

@OdinVex
Copy link

OdinVex commented Feb 2, 2025

I've changed data-root in Docker's daemon.json to a new partition and location but test 1.1.5 doesn't take that into account and still assumes to look for /var/lib/docker...

I believe 1.1.5 should only assume /var/lib/docker if the daemon.json hasn't been found or has an empty data-root, otherwise it should use that path.

(Edit: Or wherever Docker's pulling the config/parameter from.)

@konstruktoid
Copy link
Collaborator

Hi @OdinVex, this is to comply with "1.1.5 Ensure auditing is configured for Docker files and directories - /var/lib/docker" which is in the CIS Docker benchmark.
I've added a proposal to use the data-root settings instead of a static link.

@OdinVex
Copy link
Author

OdinVex commented Feb 3, 2025

Hi @OdinVex, this is to comply with "1.1.5 Ensure auditing is configured for Docker files and directories - /var/lib/docker" which is in the CIS Docker benchmark. I've added a proposal to use the data-root settings instead of a static link.

That is indeed what I meant, yes, that 1.1.5 should be updated to allow for data-root having been changed. Thank you very much for the proposal.

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

2 participants