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

Docker compose file env syntax ERROR #1142

Closed
6 tasks done
david-loe opened this issue May 3, 2024 · 1 comment · Fixed by #1143
Closed
6 tasks done

Docker compose file env syntax ERROR #1142

david-loe opened this issue May 3, 2024 · 1 comment · Fixed by #1143
Labels
status: triage Scope to be determined

Comments

@david-loe
Copy link
Contributor

Issue Description

When trying to start production docker image the following error occurs:

error while interpolating services.documenso.environment.[]: required variable NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH is missing a value: :-/opt/documenso/cert.p12

Steps to Reproduce

  1. download https://raw.githubusercontent.com/documenso/documenso/release/docker/production/compose.yml
  2. docker compose up

Expected Behavior

Running Containers

Current Behavior

Error

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Docker Compose version v2.27.0

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
@david-loe
Copy link
Contributor Author

Issue is the ? in Line 61:

      - NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH=${NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH?:-/opt/documenso/cert.p12}

after removing it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage Scope to be determined
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants