I currently build, test, and deploy a dockerized webapp through circle 1.0 and it works great (although it’s slow due to lack of layer caching). From what I understand, to continue this workflow under 2.0 I have two choices:
- use the machine executor to run basically the same flow i have in 1.0
- have a service like quay.io automatically build my container in response to a github push, and then use the docker executor to test and deploy it.
- are there any other options i’m missing here?
- if i use the machine executor is there any way to benefit from layer caching?
i love the idea of the docker executor in 2.0 but it seems crippled since it’s impossible to build dockerized apps in it. so it seems 2.0 is great for everything except dockerized apps - definitely room for improvement. but i’m also hoping i’m wrong on the above.