# Docker container using Machine executor

**URL:** <https://discuss.circleci.com/t/docker-container-using-machine-executor/23277>\
**Category:** Build Environment\
**Created:** [June 28, 2018, 6:30pm UTC](https://discuss.circleci.com/t/docker-container-using-machine-executor/23277 "2018-06-28T18:30:26Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![sujit](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@sujit](https://discuss.circleci.com/u/sujit)\
**Post date:** [June 30, 2018, 11:31am UTC](https://discuss.circleci.com/t/docker-container-using-machine-executor/23277/9 "2018-06-30T11:31:01Z")

</div>

Thanks @halfer

I have now created a new post for this, please see the below link -

> [@Working with a machine executor](https://discuss.circleci.com/t/working-with-a-machine-executor/23304):
>
> Hi Team, I have an issue when working in a workflow for a machine executor. Mine is a maven project. The test job is not recognising the build machine which is present in the build job. I don’t want to invoke my mvn package again for test, as this is a headache and increases the my pipeline time. I want to run it in a workflow so that I can distinguish both build and test separately. Could you please help me in that how I can do that in a workflow. Could you please check that and suggest how t…

---

_[View the full topic](https://discuss.circleci.com/t/docker-container-using-machine-executor/23277)._