Skip to content

fix: docker volume permission error#9953

Draft
danibarranqueroo wants to merge 1 commit intomasterfrom
PROWLER-960-jwt-key-generation-fails-with-permission-error-on-fresh-docker-compose-deployment
Draft

fix: docker volume permission error#9953
danibarranqueroo wants to merge 1 commit intomasterfrom
PROWLER-960-jwt-key-generation-fails-with-permission-error-on-fresh-docker-compose-deployment

Conversation

@danibarranqueroo
Copy link
Member

Context

When deploying Prowler using docker compose up on a fresh installation, the API container fails to start due to permission errors when attempting to write JWT RSA key files to the mounted volume.

Description

Modified docker-compose.yml to ensure a new volume is added where there will not be permission error.

Steps to review

Deploy prowler and ensure all is working as expected without permission error.

Checklist

Community Checklist
  • This feature/issue is listed in here or roadmap.prowler.com
  • Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

SDK/CLI

  • Are there new checks included in this PR? Yes / No
    • If so, do we need to update permissions for the provider? Please review this carefully.

UI

  • All issue/task requirements work as expected on the UI
  • Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px)
  • Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px)
  • Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px)
  • Ensure new entries are added to CHANGELOG.md, if applicable.

API

  • All issue/task requirements work as expected on the API
  • Endpoint response output (if applicable)
  • EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
  • Performance test results (if applicable)
  • Any other relevant evidence of the implementation (if applicable)
  • Verify if API specs need to be regenerated.
  • Check if version updates are required (e.g., specs, Poetry, etc.).
  • Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions github-actions bot added github_actions Pull requests that update GitHub Actions code component/api labels Feb 4, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

✅ All necessary CHANGELOG.md files have been updated.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/api github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant