mirror of https://github.com/DRYTRIX/TimeTracker.git synced 2026-01-06 11:40:52 -06:00

Files

Dries Peeters b880191c16 feat: add time-entry editing; improve invoices/PDF; harden Docker startup

Timer/Editing
- Add/edit time-entry UI and flows in templates (`templates/timer/*`)
- Extend timer and API routes (`app/routes/timer.py`, `app/routes/api.py`)
- Update mobile interactions (`app/static/mobile.js`)

Invoices/PDF
- Improve invoice model and route handling (`app/models/invoice.py`, `app/routes/invoices.py`)
- Enhance PDF generation and fallback logic (`app/utils/pdf_generator*.py`)
- Adjust invoice view layout (`templates/invoices/view.html`)

Docker/Startup
- Refine Docker build and startup paths (`Dockerfile`)
- Improve init/entrypoint scripts (`docker/init-database-*.py`, new `docker/entrypoint*.sh`, `docker/entrypoint.py`)
- General startup robustness and permissions fixes

Docs/UI
- Refresh README and Docker docs (setup, troubleshooting, structure)
- Minor UI/help updates (`templates/main/help.html`, `templates/projects/create.html`)
- Remove obsolete asset (`assets/screenshots/Task_Management.png`)
- Add repo hygiene updates (e.g., `.gitattributes`)

2025-09-03 09:48:19 +02:00

2.8 KiB

Raw Blame History

Docker Startup Script Troubleshooting Guide

Problem

You're getting the error: exec /app/start.sh: no such file or directory

Root Causes

This error typically occurs due to one of these issues:

Line Ending Issues: Windows CRLF line endings in shell scripts
File Permissions: Script not executable
File Not Found: Script not copied correctly during Docker build
Path Issues: Script path incorrect

Solutions

Solution 1: Use the Remote Compose (Recommended)

# Use the production remote compose with prebuilt image
docker-compose -f docker-compose.remote.yml up -d

Solution 2: Rebuild Locally

The provided Dockerfile supports local builds. If you prefer rebuilding:

docker-compose up --build -d

Solution 3: Manual Fix

If you want to fix it manually:

Check if Docker Desktop is running

Get-Service -Name "*docker*"
Start-Service -Name "com.docker.service"  # If stopped

Rebuild the Docker image

docker-compose down
docker-compose build --no-cache
docker-compose up

Check the container logs
```
docker-compose logs app
```

Solution 4: Use Simple Startup Script

The start-simple.sh script is a minimal version that should work reliably.

Debugging Steps

1. Check if the script exists in the container

docker exec -it timetracker-app ls -la /app/start.sh

2. Check script permissions

docker exec -it timetracker-app file /app/start.sh

3. Check script content

docker exec -it timetracker-app cat /app/start.sh

4. Check Docker build logs

docker-compose build --no-cache

File Structure

Dockerfile - Container build file
docker/start.sh - Startup wrapper
docker/start-simple.sh - Simple, reliable startup script
docker/start-fixed.sh - Enhanced startup script with schema fixes

Quick Test

# Test remote production image
docker-compose -f docker-compose.remote.yml up -d

# Or build locally
docker-compose up --build -d

Common Issues and Fixes

Issue: "Permission denied"

Fix: Ensure script has execute permissions

RUN chmod +x /app/start.sh

Issue: "No such file or directory"

Fix: Check if script was copied correctly

COPY docker/start-simple.sh /app/start.sh

Issue: "Bad interpreter"

Fix: Fix line endings

RUN sed -i 's/\r$//' /app/start.sh

Next Steps

Try the fixed Dockerfile first
If that works, the issue was with line endings or permissions
If it still fails, check Docker Desktop status and rebuild
Check container logs for additional error details

Support

If the issue persists, check:

Docker Desktop version and status
Windows line ending settings
Antivirus software blocking Docker
Docker daemon logs

2.8 KiB Raw Blame History