-
Notifications
You must be signed in to change notification settings - Fork 54
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
Unable to use az confcom
extention as it shows docker process was not found
#156
Comments
Hi @cYKatherine, as you mentioned, running docker inside docker is not recommended, so the azure/cli action does not support running docker commands inside. A current solution is to run these commands directly in bash. We may consider an enhancement to enable users to run Docker commands within azure/cli. |
Similar issue to #152. |
Hello @MoChilia , thank you for getting back to me. Can I confirm it is not possible to run A side question is: is there any way to run a specific Thank you so much! |
From the error message you provided, it appears that |
Thank you @MoChilia I used the instruction here: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt and it worked. For anyone who might also need this, this is how my workflow looks like:
|
Hello, I tried to use this action to run
az confcom acipolicygen --debug --approve-wildcards -a test.json --print-policy
ininlineScript
but it showed warningcli.azext_confcom.custom: The docker process was not found. Please start Docker.
I tried to check if docker was started using
systemctl | grep running
butsystemctl
wasn't installed in the docker image (I assume?).Also from this article: https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ I saw that it is not recommended to run docker inside docker, so I'm wondering does that mean there is no Docker running in this github action? Does that mean I can't run
az confcom
with this action? Is there any way to bypass this issue?Thank you so much!
The text was updated successfully, but these errors were encountered: