Got an issue? Check if listed here.
Issue:
You are likely behind a corporate or school proxy. On corporate or school computers, this is often the case. If you are in a VPN, you might also be affected.
Solution:
We recommend to use a private computer, or turn off the VPN or Proxy.
Hint:
The proxy config is usually in the file ~/.docker/config
. You might have to remove the
proxy settings from there.
See Docker documentation for more information.
Issue:
One or more containers fail to start when running docker compose up
.
Steps:
- Verify that necessary ports are not already in use.
- Check general network issues.
- Check you have enough memory available in Docker settings and on your host.
- Check you have enough disk space available in Docker settings and on your host.
- Check container logs with
docker compose logs [service_name]
to identify specific errors. Try to understand the error message and resolve the issue.
Issue:
You are likely running a command that requires elevated permissions.
Solution:
Make sure you enabled Developer Mode.
This is required to run Node.js and PHP commands. Otherwise, you might encounter EPERM
errors.
Issue:
The user and group of your host and Docker container probably mismatch. Therefore, the Docker container user doesn't have the permission to write to your competitions/
directory.
Solution:
Get your user and group ID by running id
in your terminal. You need to let Docker know about these IDs by adding them to the docker-compose.yaml
file at the competitions-manager
level. Replace 1000:1000
with your UID and GID respectively.
...
volumes:
- ./competitions:/app/data/
user: "1000:1000"
Issue:
You are likely trying to run the Docker container on an incompatible architecture.
Solution:
Make sure you are running the Docker container on a compatible architecture. Required images are available for both
amd64
and arm64
architectures, hence this is not the original of the problem.
Try re-installing Docker and make sure you are using the correct version for your CPU architecture.
- Check if someone else already had the same issue on the GitHub repository: Issues
- Create an issue on this GitHub repository here: Create Issue