Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[1.1] Build rocksdb and arm images in amd64 hosts (#5987)
* [1.1] Build rocksdb and arm images in amd64 hosts (#5954) cherry pick into 1.1 for #5947 and #5950. (#5954) When this project was started, we used base images to run some commands in the native execution environment (for example: create a user in the container). Now with cross-platform docker builds, we can use runtime emulation to do this work, and not maintain the base images. We also had an inconsistent way to house the RocksDB library files. This PR builds the libraries in parallel with the project executables, and collects the libraries with the other artifacts for the image build to use. I also updated the container images build to ubuntu 20.04 to remove all references to qemu-static container. This PR reduces (but does not completely eliminate) dependency on docker hub for the project. Tested by running E2E tests on images built on the PR branch. This checklist is used to make sure that common guidelines for a pull request are followed. - [x] I have read the [contribution guidelines](https://github.com/azure/iotedge#contributing). - [x] Title of the pull request is clear and informative. - [x] Description of the pull request includes a concise summary of the enhancement or bug fix. - [x] Pull request includes test coverage for the included changes. - Description of the pull request includes - [x] concise summary of tests added/modified - [ ] local testing done. - Open the PR in `Draft` mode if it is: - Work in progress or not intended to be merged. - Encountering multiple pipeline failures and working on fixes. _Note: We use the kodiakhq bot to merge PRs once the necessary checks and approvals are in place. When it merges a PR, kodiakhq converts the PR title to the commit title, PR description to the commit description, and squashes all the commits in the PR to a single commit. The net effect is that entire PR becomes a single commit. Please follow the best practices mentioned [here](https://chris.beams.io/posts/git-commit/#:~:text=The%20seven%20rules%20of%20a%20great%20Git%20commit,what%20and%20why%20vs.%20how%20For%20example%3A%20) for the PR title and description_ 1.1 is again slightly different than 1.2, with no consolidated artifacts, so slightly different handling of RocksDb libraries. Place rocksdb lib in a directory. Make sure destination and source are the same. no consolidated artifacts in 1.1 Processing buildx args got lost in the merge. Update to 20.04 for build image stage.
- Loading branch information