Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: S3 Backups on secondary server broken "No such container: coolify" #3458

Closed
delassiter opened this issue Sep 16, 2024 · 2 comments
Closed

[Bug]: S3 Backups on secondary server broken "No such container: coolify" #3458

delassiter opened this issue Sep 16, 2024 · 2 comments

Comments

@delassiter
Copy link

delassiter commented Sep 16, 2024 •
edited
Loading

Error Message and Logs

Error response from daemon: No such container: coolify

Steps to Reproduce

  1. Install a new server (next to your main Coolify server)
  2. Add a MariaDB instance to new server
  3. Schedule Backups for MariaDB instance with S3 enabled
  4. Click "Backup now" or wait for Backup Job to be executed

Example Repository URL

No response

Coolify Version

v4.0.0-beta.335

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.1 LTS

Additional Information

Problems with backups started occuring a couple of versions back. This issue started with v4.0.0-beta.334, I think.
@delassiter delassiter added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Sep 16, 2024
@peaklabs-dev
Copy link
Member

This has been fixed, version will be released tomorrow.

@peaklabs-dev peaklabs-dev added ✅ Done Issues that are fixed and a PR is ready to be merged. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. and removed 🔍 Triage Issues that need assessment and prioritization. labels Sep 16, 2024
@delassiter
Copy link
Author

delassiter commented Sep 16, 2024 •
edited
Loading

Thanks for the quick response and for fixing the bug! Also thank you for your amazing work!

Update: I've upgraded now and can confirm it works again.

@peaklabs-dev peaklabs-dev removed 🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Sep 17, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@delassiter @peaklabs-dev