dpkg --print-architecture is outputting the wrong text result on 64-Bit
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Raspbian |
New
|
Undecided
|
Unassigned | ||
Bug Description
BACKGROUND:
-------
I am rebuilding a RPi project that was running on 32 Bit onto RPiv4 64-Bit.
Spent all day troubleshooting docker containers on Raspbian 64-Bit. It started with me getting an error when pulling images that should have worked no problem given they do on my 32-Bit install. I was using my very stable docker compose file.
I kept getting this error: "no matching manifest for linux/arm/v8 in the manifest list entries"
Then after I started forcing the pulls using the "--platform linux/arm/v8" attribute they started coming down as expected, but then laded up in restart boot loops never able to do anything.
ISSUE:
-------
I believe I have traced the issue back to this one command "dpkg --print-
In 64-Bit is outputting "armhf" which I believe to mean 32-Bit so when this is used in scripts to set things up like source lists you land up getting the wrong software. (See attached image)
As you can see by the docker install scripts that they are using this. It is a real problem. By the amount of people reporting the issues I am having, also trying to get containers to run on arm64v8 platform. I think it is a big problem.
I am sure this is why the wrong version of docker is being installed on Raspbian 64-Bit. The solution for most people has been to use a different OS all together and dump Raspbian.
You can see some of the instructions here
https:/
https:/
(I know this is for 32-Bit but the way the scripts are written it should not matter given it checks the architecture.)
There is another bug complaining about a similar thing to do with the "dpkg --print-
https:/
| Ian K (ikill69) wrote | #1 |
| Ian K (ikill69) wrote | #2 |
Some other people have noticed the issue as well.
https:/
https:/