-
Notifications
You must be signed in to change notification settings - Fork 341
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
feat: Support custom predictor Docker image builds on non-x86 architectures #2115
base: main
Are you sure you want to change the base?
feat: Support custom predictor Docker image builds on non-x86 architectures #2115
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
37abc45
to
9c37f8e
Compare
9c37f8e
to
4d5d703
Compare
Not sure how to tag to trigger unit tests or who to ping. @sararob, I hope this isn't a bother, and please no rush. I'm Teo and I'm a first-time contributor to this project. Maybe I missed something in the different contributing docs on how to move a PR forward to the unit test/review stage. Since you've had some recent activity on |
@@ -418,6 +418,7 @@ def build_image( | |||
pip_command: str = "pip", | |||
python_command: str = "python", | |||
no_cache: bool = True, | |||
platform: str = "linux/amd64", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would prefer this flag to be set by users, rather providing a universal default.
Could we update the default to be None?
Under the assumption that only machine types with x86 processors are supported for prediction and custom training.
While currently only x86 processors are supported for prediction and custom training, this will allow users to control this behavior should that ever change in the future. Additionally, it allows users to, e.g., override the `TARGETOS` component of the `TARGETPLATFORM`.
4d5d703
to
811c0e1
Compare
Hi, can someone help taking a look at this? I would imagine you would like to support all the users using new Apple machines... @abcdefgs0324 or is there a better/correct way to do this? |
@rragundez if it helps I can also push the change suggested by @abcdefgs0324 (assuming it still applies?) |
…ges-on-64-bit-arm
To enforce the flag is set by users as opposed to providing a universal default. - See: googleapis#2115 (comment)
To enforce the flag is set by users as opposed to providing a universal default. - See: googleapis#2115 (comment)
To enable the flag to be set by users (e.g., to build images on non-x86 architectures).
f7217ff
to
6482c3c
Compare
…del-docker-images-on-64-bit-arm
26b6049
to
1e6bdea
Compare
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Note: do not merge your PR from GitHub. Adding the "ready to pull" label is the final step in the review process.
After approvals, the changes in your PR will be committed to the
main
branch and this PR will be closed.Fixes 🦕:
What
Allows users the ability to specify for which platform their custom predictor's Docker image should be built.
linux/amd64
Warning
I would imagine that, in an ideal world, we should be testing this on compatible non-x86 systems (e.g.,
arm64
andaarch64
)?Why
For library compatibility on compatible non-x86 systems (for instance, Apple Silicon).