Troubleshooting
This section covers common issues you might encounter and how to solve them.
Issue: marimo.local.dev shows an "Apache Default Page" or "It Works!"
- Symptom: You see a default web server page instead of the Marimo app.
- Cause: Another web server (like Apache or Nginx) is running directly on your host machine and is using port 80 or 443.
- Solution 1 (Recommended): Stop the conflicting service. On Linux/WSL, you can check with
sudo lsof -i :80and stop it withsudo systemctl stop apache2. - Solution 2: Change the ports used by Traefik in
docker-compose.ymlif you cannot stop the conflicting service.
Issue: The quarto container fails to build with "/app/_site": not found
- Symptom:
docker-compose buildfails with an error during theCOPY --from=builderstep. - Cause: Quarto did not generate its output into an
_sitedirectory. - Solution: Ensure your
apps/quartodirectory is a proper Quarto project by including a_quarto.ymlfile. Then, use the commandRUN quarto render .in your Dockerfile to render the entire project, which will correctly create the_siteoutput directory.
Issue: Zitadel data lost after restart
- Symptom: Your Zitadel project and apps are missing after restarting the containers.
- Cause: You ran
docker compose down -v, which removes all persistent volumes. - Solution: Only use
docker compose downto stop the containers. Do not use the-vflag unless you intend to reset all data.