Skip to content

Revert "Added support for scanning images from the docker daemon" #4291

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

Merged

Conversation

rosecodym
Copy link
Collaborator

Reverts #4276. Its new tests aren't playing nicely with our CI.

@rosecodym rosecodym requested review from a team as code owners July 3, 2025 18:19
@rosecodym rosecodym merged commit 562dd72 into main Jul 3, 2025
13 checks passed
@rosecodym rosecodym deleted the revert-4276-add_support_for_docker_daemon_as_a_source branch July 3, 2025 18:38
saghaulor added a commit to saghaulor/trufflehog that referenced this pull request Jul 10, 2025
saghaulor added a commit to saghaulor/trufflehog that referenced this pull request Jul 11, 2025
saghaulor added a commit to saghaulor/trufflehog that referenced this pull request Jul 15, 2025
…mon (trufflesecurity#4276)" (trufflesecurity#4291)"

This reverts commit 562dd72.

- Now you can scan an image directly after building it with docker build by using the docker:// prefix.
  This is ideal for local development and CI/CD pipelines that want to ensure images do not contain leaked secrets before pushing to an image registry.
- Resolves Add support for scanning images from the Docker daemon trufflesecurity#4275
saghaulor added a commit to saghaulor/trufflehog that referenced this pull request Jul 15, 2025
…mon (trufflesecurity#4276)" (trufflesecurity#4291)"

This reverts commit 562dd72.

- Now you can scan an image directly after building it with docker build by using the docker:// prefix.
  This is ideal for local development and CI/CD pipelines that want to ensure images do not contain leaked secrets before pushing to an image registry.
- Resolves Add support for scanning images from the Docker daemon trufflesecurity#4275
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

Successfully merging this pull request may close these issues.

3 participants