# Unblock O3 local deployment via docker-compose.yml? **URL:** \ **Category:** Development\ **Tags:** docker, o3\ **Created:** [October 12, 2022, 1:21am UTC](https://talk.openmrs.org/t/unblock-o3-local-deployment-via-docker-compose-yml/37678 "2022-10-12T01:21:37Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![dkayiwa](https://talk.openmrs.org/user_avatar/talk.openmrs.org/dkayiwa/32/179_2.png) [@dkayiwa](https://talk.openmrs.org/u/dkayiwa)\ **Post date:** [October 12, 2022, 2:57pm UTC](https://talk.openmrs.org/t/unblock-o3-local-deployment-via-docker-compose-yml/37678/5 "2022-10-12T14:57:29Z")
@grace i used your instructions here: [O3 Implementer Documentation: Set Up, Configure & Deploy - Projects - OpenMRS Wiki](https://wiki.openmrs.org/pages/viewpage.action?pageId=224527013#O3ImplementerDocumentation:SetUp,Configure&Deploy-QuickStartGuide:GetO3runningonyourmachinequickly) and got exactly the same problem as you did. On looking at the network tab, the call to `session` was returning a `302`. On looking at the general http headers, the `Request URL` was `http://localhost/openmrs/ws/rest/v1/session` and for the `Response Headers`, the `Location` was `http://localhost/openmrs/initialsetup` which looked like OpenMRS was still initialising. Therefore because the app tries to make REST calls before the backend is done with the startup process, you will end up breaking the application. I confirmed this by removing the docker volumes and run the docker setup afresh, but this time giving the backend time to properly start before accessing the frontend app, and all turned out well. This looks like what was reported on the ticket that you assigned to @corneliouzbett [[RA-1769] Calling REST API during initialization break Reference Application - OpenMRS Issues](https://issues.openmrs.org/browse/RA-1769) --- _[View the full topic](https://talk.openmrs.org/t/unblock-o3-local-deployment-via-docker-compose-yml/37678)._