Skip to content

Littlelink-custom for Unraid clears data after an update.  #1

Closed
Closed
Littlelink-custom for Unraid clears data after an update. #1

Description

@steRnbear87
steRnbear87
opened on Jul 14, 2022

So I created a LittleLink Custom app for UnRaid Community Appstore from the docker-compose file. My issue is whenever I update the app, it clears my current config and i have to start afresh. Reconfig after every update. Currently using it as it is with sqlite and built in mailserver.

Activity

  1. JulianPrieber
    transferred this issue fromLinkStackOrg/LinkStackon Jul 14, 2022

  2. lastsamurai26 commented on Jul 14, 2022

    @lastsamurai26
    lastsamurai26
    on Jul 14, 2022
    Member

    Can you provide us your docker-compose.yml so we can take a look at it

  3. steRnbear87 commented on Jul 14, 2022

    @steRnbear87
    steRnbear87
    on Jul 14, 2022
    Author

    littlelink-custom
    littlelink-custom1

  4. JulianPrieber commented on Jul 14, 2022

    @JulianPrieber
    JulianPrieber
    on Jul 14, 2022
    Member

    Could you try running it without Traefik?

  5. erickchung commented on Jul 14, 2022

    @erickchung
    erickchung
    on Jul 14, 2022

    I am experiencing the same problem and I don't have Traefik.
    Running only default variables.

  6. erickchung commented on Jul 15, 2022

    @erickchung
    erickchung
    on Jul 15, 2022

    I think it's everything (files, configs, sqlite db) gets wiped when the new image gets updated from docker.

    So I tried 2 things:

    1. I spun up a nginx instance and just dropped the app into www/. I converted everything over to point to my instance of mySQL hosted elsewhere on my network. Like the documentation said, I had to reseed everything and set up llc. Once everything was set up, I backed up the .env and the advanced configs. I assume that this version would be able to just get updated via the regular method.
    2. To test out docker, I shut down the nginx server and redeployed the docker image (fresh install) and uploaded the env and the config file that was pointing to mysql. All the links, pages, and settings came back but the uploaded pictures/logos didn't (I assume that it's stored in the file structure). I think it just means that if there is an update to the docker (i.e. wipe), we'll just need to upload those two configs and fix the related images to get it up and running again.

    Is there a way to isolate those config files and images to a directory that can be mapped/persisted even between wipes?
    Another thought is to add the db connection info in the docker variables and then store the env/adv configs and images in the database...

  7. steRnbear87 commented on Jul 16, 2022

    @steRnbear87
    steRnbear87
    on Jul 16, 2022
    Author

    Hey @erickchung I worked with @JulianPrieber and we were able to resolve the issue. The container app in CA appstore has been updated to prevent further updates and only take updates from the built-in updater. Let us know if you still have any issues.

  8. joaomelorodrigues commented on Jul 16, 2022

    @joaomelorodrigues
    joaomelorodrigues
    on Jul 16, 2022

    Hi, how do we map the links database in a persistent volume? Which directory?

  9. bb12489 commented on Jul 18, 2022

    @bb12489
    bb12489
    on Jul 18, 2022

    Hi, how do we map the links database in a persistent volume? Which directory?

    I would like to know this as well. I'm trying to run this on my docker swarm cluster.

  10. LinkStackOrg
    locked and limited conversation to collaborators on Jul 20, 2022
  11. JulianPrieber
    converted this issue into a discussion #2 on Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions