Title: Multi-Arch Image Support · Issue #1614 · stackrox/stackrox · GitHub
Open Graph Title: Multi-Arch Image Support · Issue #1614 · stackrox/stackrox
X Title: Multi-Arch Image Support · Issue #1614 · stackrox/stackrox
Description: First of all, congratulations on open-sourcing the project. I'm deploying Stackrox at home to play around and get used to the interface, in addition to increasing the security posture of my home-based k3s cluster. Upon installation of th...
Open Graph Description: First of all, congratulations on open-sourcing the project. I'm deploying Stackrox at home to play around and get used to the interface, in addition to increasing the security posture of my home-ba...
X Description: First of all, congratulations on open-sourcing the project. I'm deploying Stackrox at home to play around and get used to the interface, in addition to increasing the security posture of my hom...
Opengraph URL: https://github.com/stackrox/stackrox/issues/1614
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Multi-Arch Image Support","articleBody":"First of all, congratulations on open-sourcing the project. I'm deploying Stackrox at home to play around and get used to the interface, in addition to increasing the security posture of my home-based k3s cluster. Upon installation of the platform, it would appear that there is no way for the collector daemonset to run on my arm64 nodes. From a cursory look on quay.io/stackrox-io it would appear that the images that are being built are not multi-arch images. I realize that other architectures aren't necessarily popular or provide major wins in terms of business value, however for some admins the only way to experience the software first hand is to install it on a handful of Raspberry Pis running in their basement :)\r\n\r\nIn lieu of the multi arch images, I also looked at the helm chart for secured-cluster-services and also noticed that there was no way to create a nodeselector for the collector daemonset, so there's no real way for me to prevent the collector pods from ImagePullBackOff when they inevitably schedule on my arm64 nodes. (this is more of a workaround for this issue, but could very well be an issue in it's own right for the helm chart repo).\r\n\r\nIs there any interest in supporting multi-arch images moving forward? I know shoehorning multi-arch into the build process isn't always the easiest ask in the world.\r\n\r\nthanks!","author":{"url":"https://github.com/crutonjohn","@type":"Person","name":"crutonjohn"},"datePublished":"2022-05-07T04:26:28.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":17},"url":"https://github.com/1614/stackrox/issues/1614"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:ec51010f-890b-008f-6a9f-5e6de8a96a1e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9A98:2162D1:66573E:89B37E:6A504E92 |
| html-safe-nonce | 627d0bc37b4530760c6be71b2d04665e1c9f0976c13af1d20fb2f6587a826dfd |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5QTk4OjIxNjJEMTo2NjU3M0U6ODlCMzdFOjZBNTA0RTkyIiwidmlzaXRvcl9pZCI6IjExMzU3ODkzMTk5MzM0MTUwNTgiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 0790ea206a16d03ce93ea9b0c452d191e0555ba1b5deebc4374fe9f58856c629 |
| hovercard-subject-tag | issue:1228522740 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/stackrox/stackrox/1614/issue_layout |
| twitter:image | https://opengraph.githubassets.com/4ad13a3bd3b3d8279c217db458a1028f56196f1a297a2be55fc064a15163394b/stackrox/stackrox/issues/1614 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/4ad13a3bd3b3d8279c217db458a1028f56196f1a297a2be55fc064a15163394b/stackrox/stackrox/issues/1614 |
| og:image:alt | First of all, congratulations on open-sourcing the project. I'm deploying Stackrox at home to play around and get used to the interface, in addition to increasing the security posture of my home-ba... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | crutonjohn |
| hostname | github.com |
| expected-hostname | github.com |
| None | d6dc8294eb500fa36bbc57472d61fe87c522f9c3c1d64f70f4926f66a66a7efb |
| turbo-cache-control | no-preview |
| go-import | github.com/stackrox/stackrox git https://github.com/stackrox/stackrox.git |
| octolytics-dimension-user_id | 40638982 |
| octolytics-dimension-user_login | stackrox |
| octolytics-dimension-repository_id | 434017296 |
| octolytics-dimension-repository_nwo | stackrox/stackrox |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 434017296 |
| octolytics-dimension-repository_network_root_nwo | stackrox/stackrox |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 5741a45fe07e5f377d0d4c524a92e3056acc51bb |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width