You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I add a cmd into a step and it fails, the resulting error message is not really indicative of the actual problem.
Here's the relevant logs from the container after a failed request: (Note the cmd: "pip99" "install" "-r" "requirements.txt" - probably failed with something like command not found: pip99). We should see the command not found: pip99 message more prominently than (or entirely in place of) HTTP Error: 400
This is caused by a bad request via clj-docker-client with a non-existent path as CMD to the docker daemon which responds with a 400. We should read the response body not just the status code.
If I add a
cmd
into a step and it fails, the resulting error message is not really indicative of the actual problem.Here's the relevant logs from the container after a failed request: (Note the cmd:
"pip99" "install" "-r" "requirements.txt"
- probably failed with something likecommand not found: pip99
). We should see thecommand not found: pip99
message more prominently than (or entirely in place of)HTTP Error: 400
The text was updated successfully, but these errors were encountered: