FAQ and Troubleshooting
Can I use self-hosted runners for Automation jobs?
No, currently, it's not possible, but we're working on this feature.
One of the reasons to use self-hosted infrastructure is to remove resources constraints for CI runners. About Automation, this argument is less critical: The maximal possible container configuration includes 4 vCPUs and 16 GiB memory, which is typically enough for most heavyweight CI tasks.
Can I run Automation jobs on macOS or Windows?
No, currently, it's not possible. At this stage, you can Automation jobs only using Docker containers. The Docker containers, in turn, can run Linux only.
Can I access the Docker daemon from my Automation jobs?
No, it's not possible.
Can I dynamically run Docker containers from my Automation jobs?
No, currently, it's not possible. The workaround is to pre-configure the required Docker containers using services.
Do Automation steps support Docker-in-Docker?
Docker-in-Docker is not supported out of the box.
If you use Docker compose, you can use service containers. In the nearest future, we will add native support for Docker compose files.
If you want to programmatically use the Docker API, you should wait until we release support for virtual machines (as environment for running job steps).