Skip to content

Remove helix script install (partial set of Dockerfiles) #1336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 11 commits into from

Conversation

mthalman
Copy link
Member

Removing the Helix Python script install from a handful of Dockerfiles. I want to roll this out to just these Dockerfiles for now to evaluate that things are working. I have run a test build with one of the images but I want to ensure things work in the wild across these platforms.

Contributes to #1333

@mthalman mthalman requested review from a team as code owners January 31, 2025 20:29
@MichaelSimons
Copy link
Member

@dougbu - It would be good for you to review these changes.

@mthalman
Copy link
Member Author

@MichaelSimons, @dougbu - This is ready for another review.

@dougbu
Copy link
Contributor

dougbu commented Feb 10, 2025

build is failing still. could you let us know when that's cleared up❓

@MichaelSimons
Copy link
Member

build is failing still. could you let us know when that's cleared up❓

What build are you referring to?

SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]

# Install latest stable version of Python
RUN $apiUrl = 'https://api.nuget.org/v3-flatcontainer/python/index.json'; `
Copy link
Member

Choose a reason for hiding this comment

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

It does feel a little strange the the SHELL is set to powershell here yet later on a direct powershell command is executed directly. It would be nice to have consistency within this Dockerfile.

@dougbu
Copy link
Contributor

dougbu commented Feb 11, 2025

build is failing still. could you let us know when that's cleared up❓

What build are you referring to?

I saw failures in a few of the jobs, including a required one, when looking at the list of checks. resolved now — either someone retried the jobs or my window was out of date

Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

I continue to think virtualenv is the wrong approach in the Windows containers but am guessing that should be considered separate from this PR 😦 is there an issue open to use a consistent environment approach❓

@mthalman mthalman requested a review from dougbu February 12, 2025 16:05
@mthalman mthalman added the do-not-merge A PR that should not be merged yet but needs to remain open label Feb 12, 2025
@mthalman
Copy link
Member Author

I'll wait to merge this until next week when I'll have more availability to monitor the usage of these updates.

Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

looking significantly better 😀

SHELL ["cmd", "/S", "/C"]
USER ContainerAdministrator
# Install latest stable version of Python
RUN powershell -Command "`
Copy link
Contributor

Choose a reason for hiding this comment

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

no big deal but this is easier to grok than the nanoserver approach using SHELL changes

@mthalman
Copy link
Member Author

I'm going to split these changes into separate PRs to have more focused issues being addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge A PR that should not be merged yet but needs to remain open
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants