Re-introduce "latest" tags for next-gen convenience images
Customers want to always be using the latest versions of a major release (e.g., 12.x) without having to explicitly specify/change the version each time in the configuration.
Custom Machine Executor AMIs
In the same way customers can create their own custom Docker images for execution ( https://circleci.com/docs/2.0/custom-images/ ), it would be a great feature to have custom AMIs for the machine executor. Just tell us what needs to be pre-installed on these AMIs to run on your system. This is especially useful for: Cutting down build time associated with installing specific dependencies on a clean box Removing complexity associated with installing specific dependencies programmatically CCI-I-998
Support dotnet core docker images
It would be good to have docker images for dotnet core applications out of the box. CCI-I-1134
Support for ARM based Docker images.
An ARM-based executor for ARM-based Docker images would allow Raspberry Pi development as well as other ARM software. CCI-I-900
Allow amount of Disk Space for Docker Layer Caching to be increased
I have been trialing the DLC recently. It seems to work rather well and solves my problem rather nicely, until it doesn't. DLC seems to work by having its own filesystem on the container. This filesystem is limit to 50GB across the board. My use case for this feature requires Docker to have access to about 100GB of disk space. There is no way to increase this limit, even for more money. DLC is a useful feature I am willing to pay money for, but there is no option to pay more money for more disk space which would make it actually work for my use case. This means that CircleCI is losing: The upsell on the DLC feature The additional upsell on additional storage space for DLC And even potentially my team as a client because without DLC deploying via CirlceCI takes ~3.5 hours. Please, let me give you money for a very useful feature you've implemented! CCI-I-552
Cache Docker images on Docker executor
Currently, DLC only applies to the actual building of Docker images within jobs. It'd be nice to enable DLC for the actual spin up of environment Docker images, since those tend to vary wildly from just a few seconds to a few minutes. Enabling DLC will allow for consistently fast spinup of environment. CCI-I-1004
Docker Layer Cacheing optimization: Docker layer affinity for volumes
I'm currently doing a lot of work that builds a Docker image using Docker Layer Cacheing, but I'm doing so in a branch. At the same time, several other developers are also working in the same project but the Dockerfile for this image isn't yet merged. As a result, their Docker remote engines are acquiring volumes so starve my branch of cached images. This makes working in a branch really slow because it seldom chances on a volume that has the image layers available. If jobs had some kind of affinity for mounting volumes that had available image layers, this would improve branched development a ton! CCI-I-800
Nested virtualization is not supported in CircleCI VMs
ubuntu-1604:201903-01 image says “kvm: no hardware support”. My use case is: I want to build .OVA file out of .iso using packer command. So I used machine executor and running packer inside the vm.But I get following error which means that nested virtualization is not supported:Logs:Qemu stderr: Could not access KVM kernel module: No such file or directoryQemu stderr: failed to initialize KVM: No such file or directory #dmesgkvm: no hardware support Is there any way to address this issue in CircleCI? CCI-I-1194
Android x86 Emulator Support
We have recently been getting our Android build online and are running into some problems running automated simulator testing the way we do for iOS. I was curious as to whether or not we should hope to see x86 support for Android emulation any time soon. The ARM emulator extracts a pretty hefty performance penalty. CCI-I-51
Include Microsoft Visual Studio Installer Projects In Windows Images
https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects This extension provides the same functionality that currently exists in Visual Studio 2015 for Visual Studio Installer projects. To use this extension, you can either open the Extensions and Updates dialog, select the online node, and search for "Visual Studio Installer Projects Extension," or you can download directly from this page. Installing this popular extension requires an additional 4 minutes of build time for each build.