# Run only after docker built in docker hub

**URL:** <https://discuss.circleci.com/t/run-only-after-docker-built-in-docker-hub/33228>\
**Category:** Running Tests\
**Tags:** docker, circle-yml\
**Created:** [November 6, 2019, 4:48pm UTC](https://discuss.circleci.com/t/run-only-after-docker-built-in-docker-hub/33228 "2019-11-06T16:48:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sk-sahu](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/sk-sahu/32/23475_2.png) [@sk-sahu](https://discuss.circleci.com/u/sk-sahu)\
**Post date:** [November 6, 2019, 4:48pm UTC](https://discuss.circleci.com/t/run-only-after-docker-built-in-docker-hub/33228/1 "2019-11-06T16:48:37Z")

</div>

I am using a custom docker pulled from docker-hub.

So basically on each push docker builds the image and it takes time. Meanwhile, circleci pulls the previously built image instead of the latest one.

Is it possible to start running jobs only once after the docker hub built is successful?

---

<div class="post-metadata">

**Author:** ![keganlester](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/keganlester/32/23599_2.png) [@keganlester](https://discuss.circleci.com/u/keganlester)\
**Post date:** [November 7, 2019, 9:15pm UTC](https://discuss.circleci.com/t/run-only-after-docker-built-in-docker-hub/33228/2 "2019-11-07T21:15:28Z")

</div>

Hello!

Yes I believe there is a way to accomplish what you are asking but there might be a better way to tackle this problem. Are you running these on separate jobs?

---

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [November 7, 2019, 10:44pm UTC](https://discuss.circleci.com/t/run-only-after-docker-built-in-docker-hub/33228/3 "2019-11-07T22:44:36Z")

</div>

> [@sk-sahu](#):
>
> Is it possible to start running jobs only once after the docker hub built is successful?

Where is the build happening? If you are using CircleCI for your CI solution then it would make sense to build it in Circle. However you make it sound like the build is happening on a server at Docker Hub.