-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
Sqlite file incorrectly detected as unreadable #78
Comments
Also, maybe it's just my own experience, but I've found new Alpine images regularly have bugs like this in them. I know folks really like the smaller size images, but I've stopped using Alpine entirely in favor of Ubuntu or Debian slim images, which seem to have fewer regressions. I'd love to see an image of this project based on either of these, but I recognize that's a lot to ask for. |
What is your host OS and Kernel ver? Pre 5.8 gets weird if I recall. |
I'm on Ubuntu 20.04 with I'm also on |
Sometimes the version numbers don't match up. I am foggy as to when my own issue came up (I run Arch though) and if it was 5.10 that almost seems like a year ago, time flies. I do recall Alpine 3.13 and edge breaking spectacularly so the timing could be right. I do have some work to do on the db-backup image and will see what I can do about doing a deb build. My base images are built in both alpine and debian so theoretically if the same packages were installed the same routines and functions should work without any change. I'm super swamped with getting my school open this year, so likely won't have many cycles until mid October. |
Good news - this issue seems to be resolved in the latest version of the container. I'm guessing Alpine's patch for this finally made it into wherever it needed to be 🤷 |
Summary
Same issue as this -
bash
in Alpine 3.14 returns an incorrect value (false) when using[[ -r file ]]
on an otherwise readable file.Steps to reproduce
Set up a typical backup of a sqlite file, run
backup-now
, get an unreadable file error.What is the expected correct behavior?
No error, database is backed up.
Relevant logs and/or screenshots
Environment
Any logs | docker-compose.yml
Possible fixes
From the link above:
In the meantime I've found that rolling back to 2.6.1 of this tool fixes the issue, for anyone looking for a work-around.
The text was updated successfully, but these errors were encountered: