You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the badass project! Ran into an issue that I was able to work around, but wanted to suggest a feature.
It would be great to specify the architecture of docker images that should be pulled.
To give some background why this is brought up, we have a pretty old version of chef running in our environment. As a result, the only docker images published for it are amd64 architecture. This becomes a problem when trying to run on an arm64 with modern OS images.
🙍 Problem Statement
When running on arm64 (M1 Macs) and trying to test old chef versions, there is a conflict:
chef amd64 image gets pulled because it's the only one available
arm64 platform os image gets pulled because that's the host platform
This creates a conflict when trying to actually run the whole stack and I end up with
qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
(including the error just in case someone else is struggling and my workaround helps them)
❔ Possible Solution
It would be great to be able to specify architecture in line with docker's docker pull --platform option. So I imagine it to look like this
Or maybe call the option architecture not to confuse with platforms at the root level?
⤴️ Describe alternatives you've considered
I was able to solve the problem by specifying a digest for an amd64 OS image to be in line with chef. This is good in terms of having reproducible builds/tests, but might not be the desired solution in all situations.
A while ago i started experimenting with the source code of kitchen-dokken to see if this was possible, the proof of concept result is #272
This allows to satisfy my use case where we have a up-to-date infrastructure managed by chef. We build debian packages for the amd64 architecture (this is what we run in production) but our engineers have MacBook M1's with arm64 processors.
🗣️ Foreword
Thanks for the badass project! Ran into an issue that I was able to work around, but wanted to suggest a feature.
It would be great to specify the architecture of docker images that should be pulled.
To give some background why this is brought up, we have a pretty old version of chef running in our environment. As a result, the only docker images published for it are amd64 architecture. This becomes a problem when trying to run on an arm64 with modern OS images.
🙍 Problem Statement
When running on arm64 (M1 Macs) and trying to test old chef versions, there is a conflict:
This creates a conflict when trying to actually run the whole stack and I end up with
(including the error just in case someone else is struggling and my workaround helps them)
❔ Possible Solution
It would be great to be able to specify architecture in line with docker's
docker pull --platform
option. So I imagine it to look like thisOr maybe call the option
architecture
not to confuse withplatforms
at the root level?I was able to solve the problem by specifying a digest for an amd64 OS image to be in line with chef. This is good in terms of having reproducible builds/tests, but might not be the desired solution in all situations.
Example:
The text was updated successfully, but these errors were encountered: