Giter Site home page Giter Site logo

I can't backup about linkace HOT 3 CLOSED

welrbraga avatar welrbraga commented on June 7, 2024
I can't backup

from linkace.

Comments (3)

welrbraga avatar welrbraga commented on June 7, 2024

Like as expected, I've manually created the linkace-backup folder with "uid 82" as owner of this folder and the backup started to run fine.

On the first test I've created the folder (without adjust on ownership) but the log was clear (Unable to write = wrong permissions):

error production 2023-04-15 02:00:07 Unable to write file at location: linkace-backup/2023-04-15-02-00-06.zip. {"exception":"[object] (League\Flysystem\UnableToWriteFile(code: 0): Unable to write file at location: linkace-backup/2023-04-15-02-00-06.zip. at /app/vendor/league/flysystem/src/UnableToWriteFile.php:24)

After that, I changed the owner of folder from root to "82" (UID of www-data user inside container) and finally, my backup was concluded with a zip file saving the "/app" folder and a mysql dump.

from linkace.

Kovah avatar Kovah commented on June 7, 2024

Thanks for taking the time to write the detailed report. The app should already have that folder writable by default by all users because this issue was reported last year. I'll take a look to check what's the issue.

Will also update the docs to include a hint for the Cron setup.

from linkace.

Alfablos avatar Alfablos commented on June 7, 2024

Hello,
looking at the production Dockerfile I can guess that if you're running LinkAce under a "rootful" Docker installation this is expected: if you don't manually create the ./backup directory the Docker daemon creates it for you even before LinkAce does. As a result the directory's ownership is going to be "root:root" with a non permissive mode, which makes it inaccessible to LinkAce which, I assume, is not running as root.

I'd suggest to either adjust the configuration to put all the volumes in a ./volumes directory created before the containers start and then chmod that directory to the UID:GID LinkAce uses inside the container or (better) adding the user:"$UID:$GID" directive to the service in the compose file. You still have to create the volumes directory in advance and run chmod -R but you'll then be able to manage all the files because they'll be owned by you.

I hope this helps!

from linkace.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.