PI67221: Docker registry commands in the Docker deploy rule mistakenly pr epend the repository with the user name.

Fixes are available

APAR status

Closed as program error.

Error description

Docker registry commands in the Docker deploy rule
mistakenly prepend the repository with the user name.  The
user name may not be included in the repository name which
will result in failed repository access.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Systems Management         *
*                  Functions                                   *
****************************************************************
* PROBLEM DESCRIPTION: Docker registry commands in the Docker  *
*                      deploy rule mistakenly prepend the      *
*                      repository with the user name.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Docker registry commands in the Docker deploy rule mistakenly
prepend the repository with the user name.  The user name may
not be included in the repository name which will result in
failed repository access.

Problem conclusion

The Liberty Docker deploy rule is modified to remove the
prepending of the dockerUser value to the dockerRepository value
in commands.  This allows for repositories that do or do not
include the user in the dockerRepository value.  For example the
docker pull command is changed from 'docker pull
$user/${dockerRepository}:${imageName}' to 'docker pull
${dockerRepository}:${imageName}'.  If the repository name
actually includes a user name (as in a private repository), then
the user name must be included in the dockerRepository variable,
itself.

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.3.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

The deploy rules are configured in the implicit configuration of
the Liberty controller.  As such, these can be overwritten as
any other Liberty configuration in the server.xml of the
controller.

Comments

APAR Information

APAR number
PI67221
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-09
Closed date
2016-08-10
Last modified date
2016-08-10

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

R855 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI67221: Docker registry commands in the Docker deploy rule mistakenly pr epend the repository with the user name.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R855 PSY

Document Information

Share your feedback

Need support?