Skip to content

docs: Add custom Docker images documentation for multi-language support#1890

Open
haroldfabla2-hue wants to merge 2 commits into
microsoft:mainfrom
haroldfabla2-hue:docs/custom-docker-images
Open

docs: Add custom Docker images documentation for multi-language support#1890
haroldfabla2-hue wants to merge 2 commits into
microsoft:mainfrom
haroldfabla2-hue:docs/custom-docker-images

Conversation

@haroldfabla2-hue
Copy link
Copy Markdown

Description

This PR adds comprehensive documentation for building custom Docker images in Presidio, addressing issue #1663.

Changes Made

  • Added new section "Building Custom Docker Images" to
  • Documented how to modify YAML files for custom configurations
  • Added guide for supporting additional languages beyond English
  • Included troubleshooting section for common issues:
    • Memory problems when adding 10+ languages
    • NLP recognizer warnings
    • Model not found errors

Related Issue

Fixes #1663

Testing

Documentation build was verified locally.

Screenshots

N/A - Documentation only


Contributed on behalf of Silhouette Team (Alberto Farah)

Addresses issue microsoft#1663

- Added comprehensive guide for building custom Docker images
- Documented how to add support for additional languages
- Included typical pitfalls and troubleshooting tips
- Added memory optimization guidance for multi-language deployments
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

@haroldfabla2-hue please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@omri374 omri374 requested a review from Copilot May 18, 2026 08:15
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new "Building Custom Docker Images" section to docs/installation.md aimed at helping users build multi-language Presidio Docker images (issue #1663). However, the new content describes a configuration mechanism (env-var driven NER_RECOGNIZERS / DEFAULT_LANGUAGES) that does not exist in Presidio, references non-existent spaCy models, and misdescribes the repo's compose files, so it would mislead users rather than help them.

Changes:

  • New section in docs/installation.md with a custom Dockerfile, multi-language example, and troubleshooting tips.
  • Documents (fabricated) env vars NER_RECOGNIZERS / DEFAULT_LANGUAGES and uses invalid spaCy model names like es_core_web_sm.
  • Inaccurate one-liner descriptions of the existing docker-compose-*.yml files.

Comment thread docs/installation.md

#### Step 1: Modify the NLP Configuration

The primary way to add language support is through the `NER_REGOGNIZERS` environment variable. Create a custom Dockerfile:
Comment thread docs/installation.md
Comment on lines +193 to +284
The primary way to add language support is through the `NER_REGOGNIZERS` environment variable. Create a custom Dockerfile:

```dockerfile
FROM mcr.microsoft.com/presidio-analyzer:latest

# Install additional language models
RUN python -m spacy download es_core_news_lg
RUN python -m spacy download fr_core_news_lg
RUN python -m spacy download de_core_news_lg

# Set environment variables for additional languages
ENV NER_RECOGNIZERS='{"en": ["SpacyRecognizer"], "es": ["SpacyRecognizer"], "fr": ["SpacyRecognizer"], "de": ["SpacyRecognizer"]}'
ENV DEFAULT_LANGUAGES="en,es,fr,de"

CMD ["python", "-m", "presidio-analyzer"]
```

#### Step 2: Build Your Custom Image

```bash
docker build -t my-presidio-analyzer:custom -f Dockerfile .
```

#### Step 3: Run with Custom Configuration

```bash
docker run -d -p 5002:3000 \
-e NER_RECOGNIZERS='{"en": ["SpacyRecognizer"], "es": ["SpacyRecognizer"]}' \
-e DEFAULT_LANGUAGES="en,es" \
my-presidio-analyzer:custom
```

### Typical Pitfalls to Avoid

#### Memory Issues with Multiple Languages

!!! warning "Important"

Adding 10+ languages at once may cause the Docker image to run out of memory during model loading.

**Solution:** Add languages incrementally and optimize model sizes:

```dockerfile
# Use smaller models when possible
RUN python -m spacy download es_core_web_sm # Use small model
# Instead of: RUN python -m spacy download es_core_web_lg # Large model
```

Alternatively, use lazy loading for NLP models.

#### NLP Recognizer Warnings

If you see warnings like:
```
UserWarning: NLP recognizer (e.g. SpacyRecognizer, StanzaRecognizer) is not in the list of recognizers for language en.
```

**Solution:** Ensure your recognizers are properly registered in the `NER_RECOGNIZERS` configuration:

```bash
docker run -d -p 5002:3000 \
-e NER_RECOGNIZERS='{"en": ["SpacyRecognizer"], "es": ["SpacyRecognizer"]}' \
my-presidio-analyzer:custom
```

### Complete Example: Multi-Language Support

Create a `Dockerfile.multilang`:

```dockerfile
FROM mcr.microsoft.com/presidio-analyzer:latest

# Install Spanish, French, German, and Italian models
RUN python -m spacy download es_core_web_sm && \
python -m spacy download fr_core_web_sm && \
python -m spacy download de_core_web_sm && \
python -m spacy download it_core_web_sm

# Configure recognizers for all supported languages
ENV NER_RECOGNIZERS='{
"en": ["SpacyRecognizer"],
"es": ["SpacyRecognizer"],
"fr": ["SpacyRecognizer"],
"de": ["SpacyRecognizer"],
"it": ["SpacyRecognizer"]
}'
ENV DEFAULT_LANGUAGES="en,es,fr,de,it"

EXPOSE 3000

CMD ["python", "-m", "presidio-analyzer"]
```
Comment thread docs/installation.md
Comment on lines +266 to +269
RUN python -m spacy download es_core_web_sm && \
python -m spacy download fr_core_web_sm && \
python -m spacy download de_core_web_sm && \
python -m spacy download it_core_web_sm
Comment thread docs/installation.md
Comment on lines +206 to +207

CMD ["python", "-m", "presidio-analyzer"]
Comment thread docs/installation.md
Comment on lines +178 to +193
The official Presidio Docker images support English by default. To add support for additional languages, you'll need to build custom images using the provided YAML configuration files.

### Key Configuration Files

The main configuration files for customizing Presidio are located in the root directory:

- `docker-compose.yml` - Main compose file
- `docker-compose-image.yml` - Image-specific configuration
- `docker-compose-text.yml` - Text processing configuration
- `docker-compose-transformers.yml` - Transformer models configuration

### Adding Support for Additional Languages

#### Step 1: Modify the NLP Configuration

The primary way to add language support is through the `NER_REGOGNIZERS` environment variable. Create a custom Dockerfile:
Comment thread docs/installation.md
# Instead of: RUN python -m spacy download es_core_web_lg # Large model
```

Alternatively, use lazy loading for NLP models.
Comment thread docs/installation.md
If your container runs out of memory:
- Reduce the number of languages loaded simultaneously
- Use smaller spaCy models (`_sm` instead of `_lg`)
- Limit the number of NLP engine workers
Comment thread docs/installation.md
#### Step 3: Run with Custom Configuration

```bash
docker run -d -p 5002:3000 \
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

More elaborate description how to build custom Docker images for Presidio

3 participants