Closed tamenmd closed 1 year ago
How is that a bug of the Docker image?
Please include image and logs in your issue, not on some external page.
@tamenmd Any more info on this?
@tobybatch At the moment, unfortunately not. Currently, I am using Proxmox to back up the entire virtual machine, and in case of data loss, I rely on this backup for restoration. I haven't yet figured out how to integrate this plugin into my environment.
Hey @tobybatch and @kevinpapst,
Quick update on the 'Easybackup' issue in the Kimai Docker setup:
MySQL/mysqldump Fix: Managed to get MySQL and mysqldump into the container. Made a custom Docker image with this Dockerfile:
FROM kimai/kimai2:fpm-dev
RUN apk update && \
apk add mysql-client && \
rm -rf /var/lib/apt/lists/*
Rebuilt with docker build -t custom-kimai . and switched to the custom-kimai image. This seemed to fix the red quotes in EasyBackup.
Backup Issues: Still hitting some errors when trying to backup. Here's the log:
[2023-11-02 13:17:22] INFO: --- S T A R T C R E A T I N G B A C K U P ---
[2023-11-02 13:17:22] INFO: Creating backup dir '/opt/kimai/var/easy_backup/2023-11-02_131722/'.
[2023-11-02 13:17:22] INFO: Creating manifest file '/opt/kimai/var/easy_backup/2023-11-02_131722/manifest.json'.
[2023-11-02 13:17:22] INFO: Get files and dirs to backup.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/.env'.
[2023-11-02 13:17:22] INFO: It's a file. Start to copy it to '/opt/kimai/var/easy_backup/2023-11-02_131722/.env'.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/config/packages/local.yaml'.
[2023-11-02 13:17:22] WARNING: Path '/opt/kimai/config/packages/local.yaml' is not existing or not accessable.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/var/data/'.
[2023-11-02 13:17:22] INFO: It's a directory. Start to mirror it to '/opt/kimai/var/easy_backup/2023-11-02_131722/var/data/'.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/var/plugins/'.
[2023-11-02 13:17:22] INFO: It's a directory. Start to mirror it to '/opt/kimai/var/easy_backup/2023-11-02_131722/var/plugins/'.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/var/invoices/'.
[2023-11-02 13:17:22] WARNING: Path '/opt/kimai/var/invoices/' is not existing or not accessable.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/templates/invoice/'.
[2023-11-02 13:17:22] INFO: It's a directory. Start to mirror it to '/opt/kimai/var/easy_backup/2023-11-02_131722/templates/invoice/'.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/var/export/'.
[2023-11-02 13:17:22] WARNING: Path '/opt/kimai/var/export/' is not existing or not accessable.
[2023-11-02 13:17:22] INFO: Start to backup '/opt/kimai/templates/export/'.
[2023-11-02 13:17:22] INFO: It's a directory. Start to mirror it to '/opt/kimai/var/easy_backup/2023-11-02_131722/templates/export/'.
[2023-11-02 13:17:22] INFO: Start database backup.
[2023-11-02 13:17:22] INFO: Used database: 'mysql'.
[2023-11-02 13:17:22] ERROR: sh: syntax error: EOF in backquote substitution
[2023-11-02 13:17:22] INFO: No git repository recognized. Expected path: /opt/kimai/var/plugins/EasyBackupBundle/.git
Seems like there might be some file or directory issues. Also, the ERROR: sh: syntax error: EOF in backquote substitution bit is weird.
Any thoughts on these?
Thank you
I've been using the Kimai Docker integration, maintained by Toby, for my time tracking needs for quite some time now. However, I recently encountered an issue with the 'Easybackup' plugin that I would really love to get fixed.
Describe the bug When attempting to use the "Easybackup" plugin within the Kimai Docker environment, I consistently encounter the following error message: In addition to the error message, you can find the corresponding log here:
Desktop:
Docker compose file (with passwords redacted) I am using the Docker Compose file provided by Toby, which can be found here. You can see my configuration:
Additional context I'm seeking guidance on how to resolve this issue or how to configure the Docker container to include MySQL/mysqldump, allowing the "Easybackup" plugin to function correctly. If anyone has encountered a similar problem or has insights on how to configure the Docker environment to address this, please share your thoughts.
Best regards.