Introduction of Docker compose

[yashpandey06]

Description

Enhance the project by introducing Docker Compose to simplify service orchestration and deployment. This will allow contributors and users to set up the development environment more easily with a single command.

Expected Outcome

• Running docker-compose up should start all required services seamlessly.
• The application should be accessible at the appropriate ports.
• Clear documentation should guide users on setup and troubleshooting.

[Monokaix]

That's a good idea!

[Sayan4444]

Hi I had a confusion. Are we creating docker-compose.yml for development purpose? Like we hit docker compose up and all services start with hot reloading enabled?

If yes I guess we should write a new Dockerfile.yml for the both frontend and backend.The pre-written docker images are mainly for kubernetes deployment.

What I personally feel for local development, adding a simple script which starts first volcano, then both frontend and backend should be more efficient with properly written README would be better. Do tell me your thoughts

[yashpandey06]

I am making it specifically for local dev also and prod also ...industry practice is to have both in repos .

[Sayan4444]

Oh I get it, instead of deploying the docker images in k8s using volcano-dashboard.yaml, it will run individually started using docker-compose for PROD.

[Monokaix]

The dashaboard uses InClusterConfig to access kube-apiserver, so you can also deploy it in a deveploment cluster to develop locally, and if you want to use docker-compose, maybe we should add a flag like #9 (comment)?