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

docs: describe how to access the cloned repository in a Docker in Docker approach #1092

Closed
wants to merge 3 commits into from

Conversation

kayman-mk
Copy link
Collaborator

@kayman-mk kayman-mk commented Feb 22, 2024

Description

Using Docker-in-Docker gets complicated in case you want to access the cloned repository. You can't simply use . to mount it into the new container as you need to use the path from the Docker host and not from the container executing your pipeline.

I added a section with examples on how to do this easily.

Closes #532

Copy link
Contributor

Hey @kayman-mk! 👋

Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

  • the problem being solved
  • the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE.

The following ChatOps commands are supported:

  • /help: notifies a maintainer to help you out

Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command.

This message was generated automatically. You are welcome to improve it.

Copy link
Contributor

github-actions bot commented Feb 22, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 1 0 0.0s
✅ COPYPASTE jscpd yes no 1.59s
✅ JSON eslint-plugin-jsonc 1 0 0 1.24s
✅ JSON jsonlint 1 0 0.21s
✅ JSON prettier 1 1 0 0.54s
✅ JSON v8r 1 0 2.4s
✅ MARKDOWN markdownlint 1 0 0 0.42s
✅ MARKDOWN markdown-link-check 1 0 0.42s
✅ REPOSITORY checkov yes no 16.63s
✅ REPOSITORY dustilock yes no 0.46s
✅ REPOSITORY gitleaks yes no 1.05s
✅ REPOSITORY git_diff yes no 0.02s
✅ REPOSITORY grype yes no 13.45s
✅ REPOSITORY secretlint yes no 1.4s
✅ REPOSITORY syft yes no 0.32s
✅ REPOSITORY trivy-sbom yes no 1.43s
✅ REPOSITORY trufflehog yes no 13.28s
✅ SPELL cspell 9 0 2.7s
✅ TERRAFORM terraform-fmt 5 0 0 0.24s
✅ YAML prettier 1 0 0 0.48s
✅ YAML v8r 1 0 2.72s
✅ YAML yamllint 1 0 0.34s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

Copy link
Contributor

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days.

@github-actions github-actions bot added the stale Issue/PR is stale and closed automatically label Apr 30, 2024
Copy link
Contributor

This PR was closed because it has been stalled for 15 days with no activity.

@github-actions github-actions bot closed this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue/PR is stale and closed automatically
Projects
None yet
Development

Successfully merging this pull request may close these issues.

volume pb with dind
1 participant