Skip to content

Migrate dev Dockerfile to use Python virtual environment.#484

Open
Geogouz wants to merge 1 commit intorucio:masterfrom
Geogouz:patch-483-dev-venv
Open

Migrate dev Dockerfile to use Python virtual environment.#484
Geogouz wants to merge 1 commit intorucio:masterfrom
Geogouz:patch-483-dev-venv

Conversation

@Geogouz
Copy link
Contributor

@Geogouz Geogouz commented Feb 12, 2026

closes #483

Switch the dev image from system-site pip installs to a dedicated virtual environment at /opt/rucio-venv to avoid RPM/pip uninstall conflicts.

For running our tests on it.

# from rucio/containers repo root
docker build -f dev/Dockerfile -t rucio/rucio-dev:local-latest dev

# from rucio/rucio root
DOCKER_REPO=rucio RUCIO_TAG=latest RUCIO_DEV_PREFIX=local- docker compose \
  --project-name dev \
  --file etc/docker/dev/docker-compose.yml \
  --profile storage up -d

# full test run
docker exec -it dev-rucio-1 tools/run_tests.sh

@Geogouz
Copy link
Contributor Author

Geogouz commented Feb 12, 2026

Related issues: #453, #458, #478

and PRs: #467, #475, #479

ln -s $RUCIOHOME/lib/rucio /usr/local/lib/python3.9/site-packages/rucio

RUN python3 -m pip install --no-cache --upgrade fts3
RUN "$RUCIO_VENV/bin/pip" install --no-cache --upgrade pip setuptools wheel && \
Copy link
Member

Choose a reason for hiding this comment

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

In the past we had issues with pip when upgrading pip and setuptools at the same time, please split these into two upgrades again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Use a dedicated Python venv in Rucio's dev img to avoid RPM/pip package conflicts

2 participants