Skip to content

Conversation

@shwetd19
Copy link

While deploying the agent, I encountered an issue with docker run. To resolve it, I made the following changes:

  1. Dockerfile

    • Replaced pnpm-lock.yaml with package-lock.json in the dependency copy step.
    • Split RUN pnpm prune --prod && chown -R appuser:appuser /app into two separate RUN commands for clarity.
  2. ESLint Config

    • Just adjusted the formatting and import order for better consistency.

@bcherry
Copy link
Contributor

bcherry commented Oct 22, 2025

@shwetd19 are you using npm? this project is built assuming pnpm which is where the issue would probably come from. we may need to make the dockerfile more broadly compatible

@shwetd19
Copy link
Author

Hey @bcherry

Yes, I’ve just pushed the updates to the same PR!
I made the Dockerfile more broadly compatible — it now works with both pnpm and npm, using a multi-stage build to keep the final image smaller and cleaner. It automatically detects which lockfile is present and installs dependencies accordingly.

Also fixed the @typescript-eslint/eslint-plugin import issue in the ESLint config.

Thanks for pointing that out earlier — the setup should be smoother now...

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.

2 participants