@rohara I need some guidance here. I’m very frustrated. I understand this is a beta, and I have put significant time getting to where I am today. I have no complaints about the time spent - I and am very happy with it - except this one issue.
I have a fully functional multi-container
config.yml with the
docker executor for a rails engine, with a dummy react app running rspec and cucumber (including mysql and selenium/chrome).
This doc talks about multi-container execution with
docker executor, and has almost nothing with
machine. I have spent a couple hours looking over the forums etc and I see various bits of incomplete or old information; perhaps I’m missing a good doc or example project.
I don’t really have days more to spend to start from scratch to get this to work. I hope I’m wrong about most of this including starting from scratch, but I’m not finding the information I need.
- What does it mean to have to convert a project from
docker executor to
machine? What changes in the config.yml approach?
- Should I use compose instead (because I will in production)?
- Do I lose caching? How would it work with compose?
- Do I need to extract my test results for storing?
- Is there an example project that does what normally is done in the
docker executor but converted for
It is VERY frustrating to have a config that is fully fleshed out only to run into this small
shm volume size issue, which seems to mean I need to throw out all the work we did to get this running on CCI 2.0.
I hope I’ve fundamentally mistaken my situation, and will be quite happy to be wrong about it.
Any help here would be greatly appreciated.