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.

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

[Bug] AnythingLLM unproper docker-compose file config #645

Open
Xoconoch opened this issue Dec 20, 2024 · 0 comments
Open

[Bug] AnythingLLM unproper docker-compose file config #645

Xoconoch opened this issue Dec 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Xoconoch
Copy link

Describe the bug
As it is, the current docker-compose file published on the app store has a volume misconfiguration that causes the .env file to not bind properly, which breaks the installation after a version update.

To Reproduce
Steps to reproduce the behavior:

  1. Install AnythingLLM via the app store and create a user (you will have to select the "My team" option during the first boot)
  2. Change the image tag, the icon or do anything to trigger a re-composing of the container via the web-UI
  3. After it finishes re-composing, try to login using the previously created credentials, it will trigger the error "Could not validate login"

Expected behavior

If the .env file is previously binded correctly, this behavior is completely fixed. However, it is important to note that the .env file has to be created via touch or some other method in the expected location before composing the container, if it isn't and yet declared in the compose file as such:

    volumes:
      - type: bind
        source: /DATA/AppData/anythingllm/storage
        target: /app/server/storage
      # bind the .env file  
      - type: bind
        source: /DATA/AppData/anythingllm/storage/.env
        target: /app/server/.env

what will happen is that a directory named ".env" will be created instead of a file, thus failing the install. This is the reason I didn't submit a pull request to correct the docker-compose file, because I currently don't know how to workaround this error. One way I could think of is if there could be a pre-installation script added that created the .env file and then make the compose file run. If anybody's got any ideas, please hand 'em!

@Xoconoch Xoconoch added the bug Something isn't working label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant