[feat]: support build for multi-arch builds #598
Conversation
…-Code#574) * Correctly internationalize new UI access key placeholder name * Add back the keyID for non-English languages This simply replicates the existing messages so we can release the Data Limits UI without waiting for these strings to be translated. * Specify that keyId will be a number
…redictable build of shadowbox
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
@googlebot I consent. |
1 similar comment
|
@googlebot I consent. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
@alalamav @fortuna Maybe we could push experimental or unstable manifest lists until And I guess also we should hold until we can get full arm support. I don't know what the distribution is like in the wild of the different versions of arm devices. |
There are ARM's in the cloud. Could we get arch-tagged images while |
|
Any update on this? |
@JonathanDCohen closing #496 in favor of this.
With
seihonwe can easily publish the image for multiple platforms and architectures using the docker manifest feature, while providing a build template. the image that is ultimately deployed would be runnable on any of the supported platforms. By defaultseihonbuilds forarm.v6, arm.v7, arm.v8, amd64, 386however our base imagenode:8.15.0-alpinedoesn't have the arm.v7 manifest included, but the v7 architecture can run v6 build.Please let me know your thoughts on this.