Enh/podman fixes

[jfmatth]

User description

I'm a Windows user with WSL behind Podman.

Was getting a variety of errors and AI helped me fix them to run. Review and keep if you like.

Getting other async errors on resize, but not gonna fix for now.

---

PR Type

Enhancement, Bug fix

---

Description

• Remove local app volume mount for Docker compatibility

• Replace local volume paths with named volumes for images and cache

• Add named volumes definition to docker-compose.yml

• Fix entrypoint.sh line ending for Windows compatibility

---

Diagram Walkthrough

flowchart LR
  A["docker-compose.yml"] -->|Remove app volume| B["Local app mount removed"]
  A -->|Replace local paths| C["Named volumes: imgpush-images, imgpush-cache"]
  A -->|Add volumes section| D["volumes definition added"]
  E["entrypoint.sh"] -->|Fix line ending| F["Windows compatibility improved"]

Loading

File Walkthrough

	Relevant files
Configuration changes	docker-compose.yml Replace local volumes with named volumes                                  docker-compose.yml Removed version specification from docker-compose file Removed local app volume mount (./app:/app) Replaced local image and cache paths with named volumes (imgpush-images, imgpush-cache) Added volumes section to define named volumes at root level +6/-4
Bug fix	entrypoint.sh Fix line ending for Windows                                                            app/entrypoint.sh Removed trailing newline from file for Windows compatibility +1/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Data persistence risk Description: Switching from bind mounts to named volumes removes the ability to inspect and backup image and cache data from the host filesystem, potentially causing data loss during container recreation or updates without proper volume management. docker-compose.yml [8-9] Referred Code - imgpush-images:/images - imgpush-cache:/cache
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Prevent accidental image data loss In docker-compose.yml, mark the imgpush-images volume as external to prevent its accidental deletion by docker-compose and avoid potential data loss. docker-compose.yml [14-16] volumes: - imgpush-images:/images - imgpush-cache:/cache ... volumes: imgpush-images: + external: true imgpush-cache: [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a significant risk of accidental data loss with the new named volume configuration and proposes a standard, robust solution to prevent it.	High
More