Describe the bug
It looks like getting started instruction is either obsolete, or not detailed enough, or there are some problems with docker/compose files. Command docker-compose -f docker-compose.dev.yml up, mentioned in this file, can't start without additional manipulations.

*Please assign this tiket to me if it is confirmed to be a bug in docker/compose files.

To Reproduce
Steps to reproduce the behavior:

1. Check getting started instruction and try to run docker-compose -f docker-compose.dev.yml up listed there.
2. See error:

ERROR: compose.cli.main.exit_with_metrics: The Compose file is invalid because:
Service keep-backend-dev has neither an image nor a build context specified. At least one must be provided.

3. Fix this error by adding context: . to build section of keep-frontend-dev and keep-backend-dev in docker-compose.dev.yml Or alternativly we can run containers with docker compose instead of docker-compose (without dash)
4. Try docker-compose -f docker-compose.dev.yml up again and see error:

 => ERROR [8/8] RUN ln -s /usr/local/lib/node_modules/next/dist/bin/next /usr/local/bin/next                                                                                                                               0.7s
------
 > [8/8] RUN ln -s /usr/local/lib/node_modules/next/dist/bin/next /usr/local/bin/next:
0.408 ln: /usr/local/bin/next: File exists

5. Remove line RUN ln -s /usr/local/lib/node_modules/next/dist/bin/next /usr/local/bin/next from Dockerfile.dev.ui and try again
6. Now everything seems to work

Expected behavior
It is expected that commands from getting started instruction will work without any problems for as many environments as possible, even if some will have not most fresh versions of some packages.

Desktop (please complete the following information):

• OS: Ubuntu 22.04.4 LTS (Jammy Jellyfish)
• docker-compose: 1.29.2