Skip to content

Use github installation for dockerfile from dev version#20740

Merged
TomeHirata merged 5 commits intomlflow:masterfrom
TomeHirata:fix/docker-virtualenv
Feb 12, 2026
Merged

Use github installation for dockerfile from dev version#20740
TomeHirata merged 5 commits intomlflow:masterfrom
TomeHirata:fix/docker-virtualenv

Conversation

@TomeHirata
Copy link
Collaborator

@TomeHirata TomeHirata commented Feb 12, 2026

Related Issues/PRs

https://github.com/mlflow/dev/actions/runs/21907088804/job/63250153366

What changes are proposed in this pull request?

2a3b04fc7 removed virtualenv from the dockerfile, but the latest released version still requires it.

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Does this PR require updating the MLflow Skills repository?

  • No. You can skip the rest of this section.
  • Yes. Please link the corresponding PR or explain how you plan to update it.

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

What is a minor/patch release?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

… setup

This update includes the addition of 'RUN pip install virtualenv' to multiple Dockerfiles to ensure that the virtualenv package is installed, facilitating better environment management across different setups.

Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Copilot AI review requested due to automatic review settings February 12, 2026 02:56
@github-actions github-actions bot added area/build Build and test infrastructure for MLflow rn/none List under Small Changes in Changelogs. v3.9.1 labels Feb 12, 2026
@github-actions
Copy link
Contributor

🛠 DevTools 🛠

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/20740/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/20740/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/20740/merge

Copy link
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

This PR aims to unblock Docker image builds for MLflow’s virtualenv-based images by ensuring virtualenv is installed during image build, aligning the generated Dockerfile template and test Dockerfile fixtures.

Changes:

  • Add RUN pip install virtualenv to multiple Dockerfile fixtures used in tests.
  • Add RUN pip install virtualenv to the Ubuntu/pyenv setup snippet in mlflow/models/docker_utils.py so generated Dockerfiles include it.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
tests/resources/dockerfile/Dockerfile_sagemaker_virtualenv_no_java Installs virtualenv in the fixture image build steps.
tests/resources/dockerfile/Dockerfile_sagemaker_virtualenv Installs virtualenv in the fixture image build steps.
tests/resources/dockerfile/Dockerfile_no_model_uri Installs virtualenv in the fixture image build steps.
tests/resources/dockerfile/Dockerfile_java_flavor Installs virtualenv in the fixture image build steps.
tests/resources/dockerfile/Dockerfile_install_mlflow_virtualenv Installs virtualenv in the fixture image build steps.
mlflow/models/docker_utils.py Ensures generated Ubuntu-based Dockerfiles install virtualenv.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 12, 2026

Documentation preview for 35af770 is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

Copy link
Member

@harupy harupy Feb 12, 2026

Choose a reason for hiding this comment

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

Let's fix the root cause. The same issue happens again if we remove a dependency again. We can consider installing dev mlflow in Dockerfile in CI or while testing.

Copy link
Collaborator Author

@TomeHirata TomeHirata Feb 12, 2026

Choose a reason for hiding this comment

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

The same issue happens again if we remove a dependency again We can consider installing dev mlflow in Dockerfile in CI or while testing

Is it a test-only issue? Doesn't it happen when users create a Dockerfile using the dev version? We could install dev MLFlow if the dev version is used then (not only for CI or testing), but not sure if that's also an ideal behavior.

Copy link
Member

@harupy harupy Feb 12, 2026

Choose a reason for hiding this comment

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

Good question. MLflow version used in dockerfile is defined here:

return f"# Install MLflow\nRUN pip install mlflow=={VERSION}"

In >= 3.10, mlflow no longer requires virtualenv
In < 3.10, they have pip install virtualenv

I wonder if VERSION becomes < 3.10. Let's double check

Copy link
Collaborator Author

@TomeHirata TomeHirata Feb 12, 2026

Choose a reason for hiding this comment

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

Actually the dev version was used when generate-dockerfile command is called for the dev version, so the feature didn't work. I think installing the dev version from github is probably the expected behavior, wdyt?

Copy link
Member

Choose a reason for hiding this comment

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

sg!

Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Copy link
Member

@harupy harupy left a comment

Choose a reason for hiding this comment

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

LGTM!

Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
@TomeHirata TomeHirata merged commit b19301b into mlflow:master Feb 12, 2026
49 of 51 checks passed
@TomeHirata TomeHirata changed the title Add back virtualenv to fix the docker build until the next release Use github master for dockerfile from dev version Feb 13, 2026
@TomeHirata TomeHirata changed the title Use github master for dockerfile from dev version Use github installation for dockerfile from dev version Feb 13, 2026
daniellok-db pushed a commit to daniellok-db/mlflow that referenced this pull request Mar 5, 2026
daniellok-db pushed a commit that referenced this pull request Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build Build and test infrastructure for MLflow rn/none List under Small Changes in Changelogs. v3.9.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants