Support using dev-containers in a similar way as we did with the all-in-one container.
Which component of AVD is impacted
others
Use case example
For some customers it makes sense to have Docker installed on a remote environment (dedicated server/vm jump host) where the network team can connect remotely to run AVD when needed, but also use this host to run other scripts, tools, etc.
I think it'll be useful in this scenario to be able to consume the dev-containers in a similar way as we did with the all-in-one container, in the sense that they can just download the desired docker image and run it manually (e.g. using a Makefile).
If this is doable and you see some benefits, we'd need to update the docs here:
https://avd.arista.com/X.YZ/docs/containers/overview.html#how-to-use-dev-containers
Describe the solution you would like
"docker run -it" support for dev-containers.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
[X] I agree to follow this project's Code of Conduct
Enhancement summary
Support using dev-containers in a similar way as we did with the all-in-one container.
Which component of AVD is impacted
others
Use case example
For some customers it makes sense to have Docker installed on a remote environment (dedicated server/vm jump host) where the network team can connect remotely to run AVD when needed, but also use this host to run other scripts, tools, etc. I think it'll be useful in this scenario to be able to consume the dev-containers in a similar way as we did with the all-in-one container, in the sense that they can just download the desired docker image and run it manually (e.g. using a Makefile). If this is doable and you see some benefits, we'd need to update the docs here: https://avd.arista.com/X.YZ/docs/containers/overview.html#how-to-use-dev-containers
Describe the solution you would like
"docker run -it" support for dev-containers.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide