forked from Azure/iotedge
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert usage of arsing/cross to upstream cross 0.1
The fix we needed was merged into upstream a long time ago. Ref: cross-rs/cross#52 Ref: cross-rs/cross@249500e The image-linux-rust job uses cross 0.1 and not 0.2. This is because this job builds iotedge-proxy for x86_64-unknown-linux-musl, to make an iotedge-proxy Docker image for Kubernetes. We do not have a custom builder image for this target, so cross 0.2 would use upstream's image, which does not have openssl. We *could* use cross 0.2 with a custom image, like we do for the ARM targets (see Cross.toml), but for now this change just sticks with cross 0.1. The openssl in 0.1's image is still ancient (the image hasn't been updated in 4 years), but Dave said that can be tackled later, as part of updating openssl across this branch in general.
- Loading branch information
Showing
3 changed files
with
10 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters