Skip to content

fix: use upstream Dockerfile build to fix file uploads#3

Merged
gummigudm merged 1 commit into
mainfrom
fix/revert-user-node
Jun 30, 2026
Merged

fix: use upstream Dockerfile build to fix file uploads#3
gummigudm merged 1 commit into
mainfrom
fix/revert-user-node

Conversation

@gummigudm

Copy link
Copy Markdown
Collaborator

Summary

Context

PR #2 added USER node to Dockerfile.multi to fix /app/api/logs EACCES. But Dockerfile.multi doesn't pre-create /app/uploads, causing file upload failures.

The upstream publishes two images from two Dockerfiles:

  • librechatDockerfile (USER node, pre-creates all writable dirs)
  • librechat-apiDockerfile.multi (runs as root, no dir setup)

We were previously running the librechat variant. This PR aligns our build to use the same Dockerfile so we get an identical image.

Test plan

  • Merge and wait for ACR build
  • Update pinned SHA in genai-accelerator helm values
  • Deploy and verify: startup logs work, file uploads work, no EACCES errors

🤖 Generated with Claude Code

Switch CI to build from Dockerfile with target: node — the same build
procedure upstream uses for ghcr.io/danny-avila/librechat. This gives us
USER node with pre-created writable dirs (/app/uploads, /app/logs, etc.)
matching the upstream image exactly.

Revert Dockerfile.multi to match upstream (no fork-specific changes).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gummigudm gummigudm merged commit a51e2c7 into main Jun 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant