Skip to content

fix: ensure proper volume namespacing in Build Pack deployments (Fixes #2168) #5592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

Ayush9026
Copy link

@Ayush9026 Ayush9026 commented Apr 11, 2025

Submit Checklist (REMOVE THIS SECTION BEFORE SUBMITTING)

  • I have selected the next branch as the destination for my PR, not main.
  • I have listed all changes in the Changes section.
  • I have filled out the Issues section with the issue/discussion link(s) (if applicable).
  • I have tested my changes.
  • I have considered backwards compatibility.
  • I have removed this checklist and any unused sections.

Changes

  • Updated volume name generation in StartMariadb.php

  • Ensured consistent namespacing across deployment methods

Issues

fix #2168
/claim #2168

@algora-pbc algora-pbc bot added the 🙋 Bounty claim Issues or PRs that have a Bounty ready to be claimed. label Apr 11, 2025
@andrasbacsai
Copy link
Member

Hey, thanks for the PR, but it has been already fixed.

@github-actions github-actions bot removed the 🙋 Bounty claim Issues or PRs that have a Bounty ready to be claimed. label Apr 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: v4 Git repo with Build Pack: Docker Compose: volumes created with wrong name
2 participants