Feature Overview

Update container tools compat API to support Docker API.

Update Podman's tools compat API to support Docker API.  We will provide the following versions in RHEL 9.7/10.1, but only as Tech Preview at this time: 

• Docker API 1.41
• Docker API 1.43

A design doc for each version is in progress, from which a test doc can be derived.

The following versions will be delivered in a later version of RHEL, likely RHEL 9.8/10.2:

• Docker API 1.42
• Docker API 1.44
• Docker API 1.45
• Docker API 1.46

Goals

< Who benefits from this feature, and how? What is the difference between today’s current state and a world with this feature? >

Requirements

A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts.  If a non MVP requirement slips, it does not shift the feature.

(Optional) Use Cases

< How will the user interact with this feature? >

< Which users will use this and when will they use it? >

< Is this feature used as part of current user interface? >

Out of Scope

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

<Are there Upgrade considerations that customers need to account for, or that the Feature should address on behalf of the customer?>

<Does the Feature introduce data that could be gathered and used for Insights purposes?>

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

<What does success look like?>

< Does this feature have doc impact?  Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact>

 <If unsure and no Technical Writer is available, please contact Content Strategy. If yes, complete the following.>

• <What concepts do customers need to understand to be successful in [action]?>
• <How do we expect customers will use the feature? For what purpose(s)?>
• <What reference material might a customer want/need to complete [action]?>
• <Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >
• <What is the doc impact (New Content, Updates to existing content, or Release Note)?>

Interoperability Considerations

< Which other products and versions in our portfolio does this feature impact? >

<If other products will be impacted set the ‘LP_Interop’ label on the Feature>

< What interoperability test scenarios should be factored by the layered product(s)? >

Digital roadmap:

1. Include on customer viewable digital roadmap? (yes/no):
2. Customer facing summary paragraph (text customers will see on digital roadmap):
3. Type of change (specify one of: addition, change, deprecation, enhancement):
4. Related package name, if applicable:
5. If Architecture specific, specify architecture (specify x86_64, arch64, s390x, or ppc64le, leave blank if not architecture specific):

Questions