Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1374] [FEAT]: Flatpak package for Linux #875

New Issue
Closed
opened 2026-02-22 18:21:56 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:21:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @imbev on GitHub (May 12, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1374

What would you like to see?

Given dependency problems such as #898 and additional setup required to use Appimages, I suggest the building and publication of a Flatpak package to Flathub. Unlike Appimage, Flatpak "just works" on the vast majority of Linux distributions and is often available OOTB in distribution graphical app stores.

Originally created by @imbev on GitHub (May 12, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1374 ### What would you like to see? Given dependency problems such as #898 and additional setup required to use Appimages, I suggest the building and publication of a Flatpak package to Flathub. Unlike Appimage, Flatpak "just works" on the vast majority of Linux distributions and is often available OOTB in distribution graphical app stores.
yindo added the enhancementfeature requestDesktopOS: Linux labels 2026-02-22 18:21:56 -05:00
yindo closed this issue 2026-02-22 18:21:56 -05:00
yindo commented 2026-02-22 18:21:56 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 12, 2024):

The issue with the AppImage is that when the AppImage mounts, it mounts to a temp directory and that directory is read-only, but often the prisma engine needs to download for the users OS. This fails, which then fails to run the migration and client generation, which then prevents some commands from saving due to the old primsa client not knowing about new fields and preventing updates on specific columns.

If on launch, flatpak does the same, this will not resolve the issue. I have never used flatpak though

@timothycarambat commented on GitHub (May 12, 2024): The issue with the AppImage is that when the AppImage mounts, it mounts to a temp directory and that directory is read-only, but often the prisma engine needs to download for the users OS. This fails, which then fails to run the migration and client generation, which then prevents some commands from saving due to the old primsa client not knowing about new fields and preventing updates on specific columns. If on launch, flatpak does the same, this will not resolve the issue. I have never used flatpak though
yindo commented 2026-02-22 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@imbev commented on GitHub (May 12, 2024):

Flatpak has a completely different approach to building and distribution from Appimage. See https://docs.flatpak.org/

I've created a manifest that almost works, but has a permission problem. Someone more experienced with Flatpak can probably complete it. Another issue with this manifest is that it allows the network permission to allow the prisma openssl download, so the prisma issue will need to be solved before publishing to Flathub.

id: com.useanything.AnythingLLMDesktop
runtime: org.freedesktop.Platform
runtime-version: '23.08'
sdk: org.freedesktop.Sdk
sdk-extensions:
  - org.freedesktop.Sdk.Extension.node18
command: entrypoint.sh
finish-args:
  - --share=ipc
  - --socket=x11
  - --socket=fallback-x11
  - --socket=wayland
  - --device=dri
  - --share=network
  #- --filesystem=xdg-documents
modules:
  - name: entrypoint.sh
    buildsystem: simple
    build-commands:
      - install -D entrypoint.sh /app/bin/entrypoint.sh
    sources:
      - type: file
        path: entrypoint.sh
  - name: anythingllmdesktop
    buildsystem: simple
    build-commands:
      - chmod +x *.AppImage && ./AnythingLLMDesktop.AppImage --appimage-extract
      - cd squashfs-root/resources/backend/ && node node_modules/prisma generate
      - mkdir -p /app/anythingllmdesktop
      - cp -r squashfs-root/* /app/anythingllmdesktop
    sources:
      - type: file
        url: https://web.archive.org/web/20240512181948/https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.AppImage
        sha256: 792278729c870b4db3a2fd6512aee1d81e4130c1d5876d5df7e93b16bc97db65
  - name: zypak
    sources:
      - type: git
        url: https://github.com/refi64/zypak
        tag: v2024.01.17
build-options:
  append-path: /usr/lib/sdk/node18/bin
  build-args:
    - --share=network

#!/bin/sh
zypak-wrapper /app/anythingllmdesktop/AppRun
@imbev commented on GitHub (May 12, 2024): Flatpak has a completely different approach to building and distribution from Appimage. See https://docs.flatpak.org/ I've created a manifest that almost works, but has a permission problem. Someone more experienced with Flatpak can probably complete it. Another issue with this manifest is that it allows the network permission to allow the prisma openssl download, so the prisma issue will need to be solved before publishing to Flathub. ```yaml id: com.useanything.AnythingLLMDesktop runtime: org.freedesktop.Platform runtime-version: '23.08' sdk: org.freedesktop.Sdk sdk-extensions: - org.freedesktop.Sdk.Extension.node18 command: entrypoint.sh finish-args: - --share=ipc - --socket=x11 - --socket=fallback-x11 - --socket=wayland - --device=dri - --share=network #- --filesystem=xdg-documents modules: - name: entrypoint.sh buildsystem: simple build-commands: - install -D entrypoint.sh /app/bin/entrypoint.sh sources: - type: file path: entrypoint.sh - name: anythingllmdesktop buildsystem: simple build-commands: - chmod +x *.AppImage && ./AnythingLLMDesktop.AppImage --appimage-extract - cd squashfs-root/resources/backend/ && node node_modules/prisma generate - mkdir -p /app/anythingllmdesktop - cp -r squashfs-root/* /app/anythingllmdesktop sources: - type: file url: https://web.archive.org/web/20240512181948/https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.AppImage sha256: 792278729c870b4db3a2fd6512aee1d81e4130c1d5876d5df7e93b16bc97db65 - name: zypak sources: - type: git url: https://github.com/refi64/zypak tag: v2024.01.17 build-options: append-path: /usr/lib/sdk/node18/bin build-args: - --share=network ``` ```bash #!/bin/sh zypak-wrapper /app/anythingllmdesktop/AppRun ```
yindo commented 2026-02-22 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@imbev commented on GitHub (May 16, 2024):

@timothycarambat Is there an all-in-one build that's not the appimage?

@imbev commented on GitHub (May 16, 2024): @timothycarambat Is there an all-in-one build that's not the appimage?
yindo commented 2026-02-22 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 16, 2024):

@imbev the docker image - but that is it. We dont publish multiple linux desktop wrappers

@timothycarambat commented on GitHub (May 16, 2024): @imbev the docker image - but that is it. We dont publish multiple linux desktop wrappers
yindo commented 2026-02-22 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@zaro commented on GitHub (Oct 10, 2024):

Just leaving this for reference : https://github.com/zaro/anything-llm-flatpak/ has a working flatpak package.

@timothycarambat If you are interested I can help with publishing on Flathub.

@zaro commented on GitHub (Oct 10, 2024): Just leaving this for reference : https://github.com/zaro/anything-llm-flatpak/ has a working flatpak package. @timothycarambat If you are interested I can help with publishing on Flathub.
yindo commented 2026-02-22 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@MrRulf commented on GitHub (Aug 28, 2025):

Why was this issue closed?

I also'd like to point out that the AppImage isn't exactly treated like a normal AppImage, considering the need to unpack etc.

And that is one of the main painpoints for me, a custom installation method for anythingllm. I understand focusing on one method and I think AppImages are reasonable, there may be no package manager for them, but considering they stay within their file they are manageable in other ways.

So maybe this is the wrong issue for the problem I see, but I think the installation method should be reconsidered to either make it work like a normal AppImage (afaik thats not the case right now because of some read/write issues) or change it to something else without that problem, possibly flatpak (or add and keep both).

Please don't take this the wrong way if my english is bad, the purpose of my comment is to show a problem that I see and suggest a solution, not to tell u u have to do this because I want u to.

@MrRulf commented on GitHub (Aug 28, 2025): Why was this issue closed? I also'd like to point out that the AppImage isn't exactly treated like a normal AppImage, considering the need to unpack etc. And that is one of the main painpoints for me, a custom installation method for anythingllm. I understand focusing on one method and I think AppImages are reasonable, there may be no package manager for them, but considering they stay within their file they are manageable in other ways. So maybe this is the wrong issue for the problem I see, but I think the installation method should be reconsidered to either make it work like a normal AppImage (afaik thats not the case right now because of some read/write issues) or change it to something else without that problem, possibly flatpak (or add and keep both). Please don't take this the wrong way if my english is bad, the purpose of my comment is to show a problem that I see and suggest a solution, not to tell u u have to do this because I want u to.
yindo changed title from [FEAT]: Flatpak package for Linux to [GH-ISSUE #1374] [FEAT]: Flatpak package for Linux 2026-06-05 14:37:41 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Desktop OS: Linux enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#875
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?