starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

documenso`. I consistently get a `manifest unknown` error for both `:edge` and `:v2.9.0` tags. #540

New issue

Closed

opened 2026-02-26 18:47:29 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 18:47:29 +03:00

Owner

Originally created by @lucasananou on GitHub (Jun 26, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1859

Issue Description

Hello,

I have an issue pulling any image from ghcr.io/documenso/documenso. I consistently get a manifest unknown error for both :edge and :v2.9.0 tags.

However, I can successfully pull other public images from ghcr.io, for example ghcr.io/github/super-linter:latest.

This proves the problem is specific to the documenso/documenso repository and not my server's general connectivity to ghcr.io. My diagnostic tests (dig, curl) are all clean.

Could there be a replication or manifest corruption issue on your repository?

Thank you.

Steps to Reproduce

No response

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @lucasananou on GitHub (Jun 26, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1859 ### Issue Description Hello, I have an issue pulling any image from `ghcr.io/documenso/documenso`. I consistently get a `manifest unknown` error for both `:edge` and `:v2.9.0` tags. However, I can successfully pull other public images from `ghcr.io`, for example `ghcr.io/github/super-linter:latest`. This proves the problem is specific to the `documenso/documenso` repository and not my server's general connectivity to `ghcr.io`. My diagnostic tests (dig, curl) are all clean. Could there be a replication or manifest corruption issue on your repository? Thank you. ### Steps to Reproduce _No response_ ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [ ] I have searched the existing issues to make sure this is not a duplicate. - [ ] I have provided steps to reproduce the issue. - [ ] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:29 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 26, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jun 26, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:30 +03:00

Author

Owner

@lucasananou commented on GitHub (Jun 26, 2025):

Hello Documenso Team,

I have spent the last 10+ hours attempting to set up a new self-hosted instance of Documenso on a clean server, with the goal of using the API for automation. Unfortunately, I encountered a series of critical issues at every possible step, making it impossible to get a working instance with a usable API.

I am documenting them here in detail in the hope that it helps you fix these problems for future users.

My Environment:

Server: Ubuntu 22.04 on a VPS

Docker: Installed via the official Docker repository.

Problem 1: Unable to Pull Images from GitHub Container Registry (ghcr.io)
My first approach was to use the recommended Docker images from ghcr.io. All attempts failed.

Action:

Bash

Attempt 1

sudo docker pull ghcr.io/documenso/documenso:edge

Attempt 2

sudo docker pull ghcr.io/documenso/documenso:v2.9.0
Result (for all tags):
The command fails consistently with the error:

Error response from daemon: manifest unknown
Crucial Evidence:
This is not a general network or Docker issue on my server. I can successfully pull other public images from ghcr.io. This command worked perfectly:

Bash

sudo docker pull ghcr.io/github/super-linter:latest

--> This downloads successfully.

Conclusion: The issue is specific to the documenso/documenso repository on ghcr.io, which seems to be inaccessible or corrupted for some users/regions.

Problem 2: Docker Hub Image (:latest) Has No Usable API
As a fallback, I tried the image from Docker Hub.

Action:

Bash

This command works successfully

sudo docker pull documenso/documenso:latest

I then successfully launched the stack using docker-compose.

The container is UP and running.

sudo docker compose --env-file .env -f docker/production/compose.yml ps

--> Shows both database and documenso containers as Up/Healthy.

Result:
While the application is running, the API is completely unresponsive. All attempts to reach documented API endpoints for document creation result in a 404 Not Found.

Evidence (Curl test from the host):

Bash

curl -v -X POST http://127.0.0.1:3000/api/v1/envelopes
-H "Authorization: Bearer <my_api_token>"
-H "Content-Type: application/json"
-d '{"templateId": 1}'

Result:

< HTTP/1.1 404 Not Found
< content-type: application/json
< content-length: 23
<
{"message":"Not Found"}
I have tested all possible endpoint variations (/submissions, /templates/1/envelopes, etc.) with both GET and POST methods. They all return 404 Not Found.

Conclusion: The documenso/documenso:latest image on Docker Hub, while it runs, does not seem to expose any of the documented V1 API routes.

Problem 3: Building from Source Fails
As a last resort, I attempted to build the image from the main branch source code. This also failed due to several issues in the repository.

Sub-problem 3a: Out-of-sync lockfile

Action: sudo docker build -f apps/remix/Dockerfile .

Error: The build fails at the RUN npm ci step because package.json and package-lock.json are out of sync (EUSAGE error).

Workaround: I had to edit the Dockerfile to replace npm ci with npm install.

Sub-problem 3b: Missing bash dependency

Error: After fixing the npm ci issue, the build failed at the RUN npm run build step with the error env: can't execute 'bash': No such file or directory.

Workaround: I had to edit the Dockerfile again to add RUN apk add --no-cache bash before the RUN npm run build step in the build-env stage.

Sub-problem 3c: Code-level Typecheck failure

Error: After fixing the two issues above, the build still fails during npm run build with exit code 2. The logs indicate a Lifecycle script 'typecheck' failed error.

Conclusion: The code currently in the main branch does not pass its own type checks and is therefore un-buildable.

@lucasananou commented on GitHub (Jun 26, 2025): Hello Documenso Team, I have spent the last 10+ hours attempting to set up a new self-hosted instance of Documenso on a clean server, with the goal of using the API for automation. Unfortunately, I encountered a series of critical issues at every possible step, making it impossible to get a working instance with a usable API. I am documenting them here in detail in the hope that it helps you fix these problems for future users. My Environment: Server: Ubuntu 22.04 on a VPS Docker: Installed via the official Docker repository. Problem 1: Unable to Pull Images from GitHub Container Registry (ghcr.io) My first approach was to use the recommended Docker images from ghcr.io. All attempts failed. Action: Bash # Attempt 1 sudo docker pull ghcr.io/documenso/documenso:edge # Attempt 2 sudo docker pull ghcr.io/documenso/documenso:v2.9.0 Result (for all tags): The command fails consistently with the error: Error response from daemon: manifest unknown Crucial Evidence: This is not a general network or Docker issue on my server. I can successfully pull other public images from ghcr.io. This command worked perfectly: Bash sudo docker pull ghcr.io/github/super-linter:latest # --> This downloads successfully. Conclusion: The issue is specific to the documenso/documenso repository on ghcr.io, which seems to be inaccessible or corrupted for some users/regions. Problem 2: Docker Hub Image (:latest) Has No Usable API As a fallback, I tried the image from Docker Hub. Action: Bash # This command works successfully sudo docker pull documenso/documenso:latest # I then successfully launched the stack using docker-compose. # The container is UP and running. sudo docker compose --env-file .env -f docker/production/compose.yml ps # --> Shows both database and documenso containers as Up/Healthy. Result: While the application is running, the API is completely unresponsive. All attempts to reach documented API endpoints for document creation result in a 404 Not Found. Evidence (Curl test from the host): Bash curl -v -X POST http://127.0.0.1:3000/api/v1/envelopes \ -H "Authorization: Bearer <my_api_token>" \ -H "Content-Type: application/json" \ -d '{"templateId": 1}' # Result: < HTTP/1.1 404 Not Found < content-type: application/json < content-length: 23 < {"message":"Not Found"} I have tested all possible endpoint variations (/submissions, /templates/1/envelopes, etc.) with both GET and POST methods. They all return 404 Not Found. Conclusion: The documenso/documenso:latest image on Docker Hub, while it runs, does not seem to expose any of the documented V1 API routes. Problem 3: Building from Source Fails As a last resort, I attempted to build the image from the main branch source code. This also failed due to several issues in the repository. Sub-problem 3a: Out-of-sync lockfile Action: sudo docker build -f apps/remix/Dockerfile . Error: The build fails at the RUN npm ci step because package.json and package-lock.json are out of sync (EUSAGE error). Workaround: I had to edit the Dockerfile to replace npm ci with npm install. Sub-problem 3b: Missing bash dependency Error: After fixing the npm ci issue, the build failed at the RUN npm run build step with the error env: can't execute 'bash': No such file or directory. Workaround: I had to edit the Dockerfile again to add RUN apk add --no-cache bash before the RUN npm run build step in the build-env stage. Sub-problem 3c: Code-level Typecheck failure Error: After fixing the two issues above, the build still fails during npm run build with exit code 2. The logs indicate a Lifecycle script 'typecheck' failed error. Conclusion: The code currently in the main branch does not pass its own type checks and is therefore un-buildable.

kerem commented

2026-02-26 18:47:30 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

Hi, @lucasananou

I investigated your issue and there's a few stuff I came across.

v2.9.0 tag doesn't exist, the latest release is v1.12.1, no v2.x versions exist
No "edge" builds in ghcr.io. Docker publishing workflow only runs on release branch. There is no continuous builds from main branch with edge tag. ghcr.io images exist for: latest, git SHA, and version tags (v1.x.x)
Build requires bash. apps/remix/.bin/build.sh:1 uses #!/usr/bin/env bash, Alpine Linux doesn't include bash by default
Wrong API endpoint. You tried /api/v1/envelopes - this doesn't exist. The correct endpoints are: /api/v1/documents, /api/v1/templates

@ephraimduncan commented on GitHub (Aug 23, 2025): Hi, @lucasananou I investigated your issue and there's a few stuff I came across. 1. v2.9.0 tag doesn't exist, the latest release is v1.12.1, no v2.x versions exist 2. No "edge" builds in ghcr.io. Docker publishing workflow only runs on release branch. There is no continuous builds from main branch with edge tag. `ghcr.io` images exist for: latest, git SHA, and version tags (v1.x.x) 3. Build requires bash. `apps/remix/.bin/build.sh`:1 uses `#!/usr/bin/env bash`, Alpine Linux doesn't include bash by default 4. Wrong API endpoint. You tried `/api/v1/envelopes` - this doesn't exist. The correct endpoints are: `/api/v1/documents`, `/api/v1/templates`

kerem referenced this issue

2026-02-26 19:31:33 +03:00

[PR #540] [CLOSED] chore(deps-dev): bump @types/node from 20.1.0 to 20.8.3 in /apps/web #1031

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#540

No description provided.

Rows
Columns

[GH-ISSUE #1859] have an issue pulling any image from ghcr.io/documenso/documenso. I consistently get a manifest unknown error for both :edge and :v2.9.0 tags. #540

Issue Description

Steps to Reproduce

Expected Behavior

Current Behavior

Screenshots (optional)

Operating System [e.g., Windows 10]

Browser [e.g., Chrome, Firefox]

Version [e.g., 2.0.1]

Please check the boxes that apply to this issue report.

Attempt 1

Attempt 2

--> This downloads successfully.

This command works successfully

I then successfully launched the stack using docker-compose.

The container is UP and running.

--> Shows both database and documenso containers as Up/Healthy.

Result:

[GH-ISSUE #1859] have an issue pulling any image from `ghcr.io/documenso/documenso`. I consistently get a `manifest unknown` error for both `:edge` and `:v2.9.0` tags. #540