Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DevOps Task fails when using 'runCmd'
See original GitHub issueAll uses of the latest DevOps Marketplace extension (as of update 17/11/2022) are failing when the ‘runCmd’ parameter is provided.
Regardless of what is provided for the parameter, the following error is returned:
Command failed: docker ps -q -a --filter label=devcontainer.local_folder=/home/vsts/work/1/s (exit code: undefined).
Issue Analytics
- State:
- Created 10 months ago
- Comments:9
Top Results From Across the Web
Review logs to diagnose pipeline issues - Azure
You can view logs by navigating to the pipeline run summary and selecting the job and task. If a certain task is failing,...
Read more >Batch file fails on Azure DevOps Command Line task [duplicate]
However, when I run the same using cmd /c $(Build.SourcesDirectory\SessionTest.bat from the Azure DevOps pipeline, I get the following output:
Read more >AWS SSM Run Command Task
When the command fails one more time beyond the value of MaxErrors, the systems stops sending the command to additional targets. You can...
Read more >The Azure CLI Task does not fail when a command fails #10125
We have run into this issue with a customer project that looking to bring a large Heroku app into Azure and Azure DevOps....
Read more >Solution for running scheduled task with 'run whether user is ...
Solution for running scheduled task with 'run whether user is logged on or ... Run "cmd /c powershell.exe -ExecutionPolicy Bypass -NoLogo ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Glad that is working now! I’ve created #185 to track improving the error output
@stuartleeks That seems to have resolved the issue! It was the
set_docker_sock_permission.shcausing the issue! Thanks for the support!