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

fix: suggestion for volume mount issue #8

Closed

Conversation

GangGreenTemperTatum
Copy link
Contributor

i believe this should mitigate a problem i found when using volume for containers:

➜  .robopages robopages run --function zap_baseline_scan
>> enter value for argument 'target': https://scanme.nmap.org/

[2024-11-07T21:20:51Z WARN ] executing: /usr/local/bin/docker run --rm -v${HOME}:/zap/wrk --net=host zaproxy/zap-stable -t https://scanme.nmap.org/ zap_headless_scan
>> enter 'y' to proceed or any other key to cancel: y


EXIT CODE: exit status: 125
ERROR: docker: Error response from daemon: create ${HOME}: "${HOME}" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.

please noob me if this is not the case :) i also receive the same result with sql_map example and is not specific to my WIP robopage

@evilsocket
Copy link
Collaborator

@GangGreenTemperTatum the problem here is that the volume seems mapped to relative path which is not allowed, the double argument push is wrong

@evilsocket evilsocket closed this Nov 7, 2024
@GangGreenTemperTatum
Copy link
Contributor Author

@GangGreenTemperTatum the problem here is that the volume seems mapped to relative path which is not allowed, the double argument push is wrong

totally makes sense, thank you! :)

@evilsocket
Copy link
Collaborator

mmm in the error message i see ${HOME}, while i see $HOME in the YML ... how did this happen? :D

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.

2 participants