Bug 1212223 - BCI container architecture decision unclear
Summary: BCI container architecture decision unclear
Status: RESOLVED FIXED
Alias: None
Product: Documentation
Classification: Non-product-specific documentation
Component: Container (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Dmitri Popov
QA Contact: Tanja Roth
URL:
Whiteboard: https://jira.suse.com/browse/DOCTEAM-...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-12 08:55 UTC by Dennis Knorr
Modified: 2023-07-12 12:59 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Knorr 2023-06-12 08:55:24 UTC 
In https://documentation.suse.com/smart/container/html/concept-bci-get-started/index.html there's something strange which i do not understand.

For obtaining the architecture of the container for SLE BCI we have the following command:

"""
arch="$(uname -p|sed 's/x86_64/amd64/')"
"""

But this would also replace every intel architecture with an AMD architecture. I am not sure if this is a bug.

Perhaps we just compile everything for x86_64/amd64 compatible so we can do that, but i do not really understand the reasoning, or if it is indeed a bug.
Comment 1 Tanja Roth 2023-06-23 13:29:24 UTC 
Thank you for the bug report, Dennis! It being tracked and processed as part of our queue.
Comment 2 Dan Čermák 2023-07-07 13:07:15 UTC 
(In reply to Dennis Knorr from comment #0)
> In
> https://documentation.suse.com/smart/container/html/concept-bci-get-started/
> index.html there's something strange which i do not understand.
> 
> For obtaining the architecture of the container for SLE BCI we have the
> following command:
> 
> """
> arch="$(uname -p|sed 's/x86_64/amd64/')"
> """
> 
> But this would also replace every intel architecture with an AMD
> architecture. I am not sure if this is a bug.
> 
> Perhaps we just compile everything for x86_64/amd64 compatible so we can do
> that, but i do not really understand the reasoning, or if it is indeed a bug.

To be honest, I don't recall why I added the sed call into the documentation. I guess it was to match the output of dpkg --print-architecture exactly. But you're right, it doesn't really make sense
Comment 3 Dan Čermák 2023-07-07 13:11:40 UTC 
https://github.com/SUSE/doc-modular/pull/173