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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
you can do this in AKS by mounting /var/run/docker.sock with hostpath. However there is no hostpath param for ACI. Is there any equivalent operation for ACI?
This issue: microsoft/azure-pipelines-agent#2056 seems to suggest this can be done by specifying "options" but as far as I can tell there is no options command for ACI either.
Clearly docker is running on the vm, how can I get this docker in docker functionality for ACI?
Thanks!!
The text was updated successfully, but these errors were encountered:
The current ACI documentation indicates that container instances now run with full hypervisor isolation for security (no shared host). If that's the case, there's no technical reason an ACI container couldn't be run in privileged mode, which would allow for docker-in-docker to work.
The use case of being able to instantiate ACI instances for surge building and performing builds inside a container would be a massive gamechanger for CI.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, how can I run docker commands such as building a docker image, inside an azure container instance, that is itself running a docker image?
According to this link: https://stackoverflow.com/questions/52973546/docker-in-docker-in-aks
you can do this in AKS by mounting /var/run/docker.sock with hostpath. However there is no hostpath param for ACI. Is there any equivalent operation for ACI?
This issue: microsoft/azure-pipelines-agent#2056 seems to suggest this can be done by specifying "options" but as far as I can tell there is no options command for ACI either.
Clearly docker is running on the vm, how can I get this docker in docker functionality for ACI?
Thanks!!
The text was updated successfully, but these errors were encountered: