Skip to content

Commit

Permalink
add pip alternative
Browse files Browse the repository at this point in the history
  • Loading branch information
djohts committed Aug 30, 2024
1 parent 96dbd48 commit dd1353c
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion python.Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -27,14 +27,18 @@ RUN ./configure --enable-optimizations --enable-loadable-sqlite-extensions && \
make PROFILE_TASK="-m test.regrtest --pgo -j8" -j8 && \
make altinstall

# update alternatives
# update python alternatives
RUN update-alternatives --install /usr/bin/python python /usr/local/bin/python$PYTHON_VERSION_SHORT 1 && \
update-alternatives --set python /usr/local/bin/python$PYTHON_VERSION_SHORT

# install pip
RUN python -m ensurepip --upgrade && \
python -m pip install --upgrade pip

# update pip alternatives
RUN update-alternatives --install /usr/bin/pip pip /usr/local/bin/pip$PYTHON_VERSION_SHORT 1 && \
update-alternatives --set pip /usr/local/bin/pip$PYTHON_VERSION_SHORT

ENV USER container

Check warning on line 42 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.8.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 42 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.9.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 42 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.10.14)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 42 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.11.9)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 42 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.12.5)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV USER container

Check warning on line 43 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.8.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 43 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.9.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 43 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.10.14)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 43 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.11.9)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 43 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.12.5)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV HOME /home/container

Check warning on line 44 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.8.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 44 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.9.19)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 44 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.10.14)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 44 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.11.9)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 44 in python.Dockerfile

View workflow job for this annotation

GitHub Actions / python (3.12.5)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Expand Down

0 comments on commit dd1353c

Please sign in to comment.