Frontend cannot to Render Inline Formulas When Using Docker Self-Host

[Dave0126]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Related Issues and PRs

• Issue #27062
• PR #27070

Issues Description

• When starting the containers using the docker-compose.yaml file from the main branch, the web container pulls its image as defined in ./docker/docker-compose.yaml#L692

docker inspect langgenius/dify-web:1.9.2 

[
    {
        "Id": "sha256:f09fba9988fdaf623f9dc2902190120886da321c52a1d42ad8d9dfba811c6222",
        "RepoTags": [
            "langgenius/dify-web:1.9.2"
        ],
        "RepoDigests": [
            "langgenius/dify-web@sha256:f09fba9988fdaf623f9dc2902190120886da321c52a1d42ad8d9dfba811c6222"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2025-10-29T04:33:38.387546299Z",
        "DockerVersion": "",
        "Author": "",
        "Architecture": "arm64",
        "Os": "linux",
        "Size": 183017877,
...

• According to PR #27070, the environment variable NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX was added to set whether inline formulas are rendered. Many thanks for this contribution.

• However, in ./docker/docker-compose.yaml#L695-L716, this variable is not included — neither NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX nor *shared-api-worker-env is referenced. As a result, the configuration in .env does not take effect.

• After I set the environment variable directly in the environment block as NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX: true, inline formulas still do not render correctly — see the screenshot below.

✔️ Expected Behavior

The inline formula block should be rendered.

❌ Actual Behavior

• Subsequently, I built a custom image as custom-dify-web:1.9.2 for the web container and replaced the one defined at docker/docker-compose.yaml#L692

    build:
      context: ../web
      dockerfile: Dockerfile
    image: custom-dify-web:1.9.2

Suggested Actions:

1. Please update the Docker image tagged as langgenius/dify-web:1.9.2.
2. Include the environment variable NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX in ./docker/docker-compose.yaml#L695-L716.

[dosubot]

Hi @Dave0126! I'm Dosu and I’m helping the dify team.

The inline formula rendering in Dify's frontend requires the environment variable NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX to be set at build time, not just at runtime. This is because Dify uses Next.js, which embeds NEXT_PUBLIC_ variables into the static frontend during the build process. Setting this variable in your Docker Compose environment or .env file after the image is built will not enable the feature in the official langgenius/dify-web:1.9.2 image (details, code reference).

To enable inline formula rendering, you need to build the frontend image yourself with NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX=true set in the build environment. Here’s how you can do it:

1. Clone the Dify repo and go to the web directory.
2. Create or edit a .env file in web/ and set:

   NEXT_PUBLIC_ENABLE_SINGLE_DOLLAR_LATEX=true
   

3. Build the frontend image:

   docker build -t custom-dify-web:1.9.2 .
   

4. In your docker-compose.yaml, use your custom image for the web service:

   web:
     image: custom-dify-web:1.9.2
     ...

5. Restart your containers.

This will ensure the variable is present at build time and inline formulas will render as expected. If you use the official image, this feature will remain disabled until the maintainers publish an updated image built with the variable enabled (PR #27070).

Note: Enabling single-dollar inline LaTeX can cause conflicts with regular text, so use with care in production environments.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}