# Using a new 'Workflow' in my config.yaml file

**URL:** <https://discuss.circleci.com/t/using-a-new-workflow-in-my-config-yaml-file/36980>\
**Category:** Build Environment\
**Created:** [August 8, 2020, 12:35am UTC](https://discuss.circleci.com/t/using-a-new-workflow-in-my-config-yaml-file/36980 "2020-08-08T00:35:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![wcneill](https://avatars.discourse-cdn.com/v4/letter/w/b19c9b/32.png) [@wcneill](https://discuss.circleci.com/u/wcneill)\
**Post date:** [August 8, 2020, 5:44am UTC](https://discuss.circleci.com/t/using-a-new-workflow-in-my-config-yaml-file/36980/2 "2020-08-08T05:44:43Z")

</div>

I’m gonna answer my own question!

So I figured that since each “job” gets its own docker, that they probably aren’t the same one, and that I lose the docker from the `build` job when that job is finished. Sure enough, I have to re-run the commands to make the virtual environment AND re-install my dependencies.

That fixed it, and now I have another [question here](https://discuss.circleci.com/t/can-you-pass-a-docker-and-virtual-environment-from-one-job-to-the-next/36982): Can I pass the docker from the `build` job to the `test` job, since all of the requirements and such are the same?

---

_[View the full topic](https://discuss.circleci.com/t/using-a-new-workflow-in-my-config-yaml-file/36980)._