Incremental docker image updates misconfigures container entrypoint and cmd

Bug #1906914 reported by Dan Voiculeasa
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Dan Voiculeasa

Bug Description

Brief Description
-----------------

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------

Expected Behavior
------------------
${MY_REPO}/build-tools/build-docker-images/update-stx-image.sh keeps the original CMD and ENTRYPOINT of the container.

inspect:
"Cmd": [
    "/bin/bash"
],
"Entrypoint": null,

Since null cannot be generated the following entrypoint seems acceptable:
"Entrypoint": [
    ""
],

Actual Behavior
----------------
${MY_REPO}/build-tools/build-docker-images/update-stx-image.sh doesn't keep the original CMD and ENTRYPOINT of the container.

inspect:
"Cmd": [
    "/bin/sh",
    "-c",
    "/bin/bash"
],
"Entrypoint": [
    "/bin/bash"
],

Reproducibility
---------------
100%

System Configuration
--------------------
build-tools

Branch/Pull Time/Commit
-----------------------
Nov 2020

Last Pass
---------

Timestamp/Logs
--------------

Test Activity
-------------
Developer Testing

Workaround
----------

Changed in starlingx:
assignee: nobody → Dan Voiculeasa (dvoicule)
Ghada Khalil (gkhalil)
tags: added: stx.5.0 stx.tools
Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
tags: added: stx.build
Revision history for this message
Dan Voiculeasa (dvoicule) wrote :
Changed in starlingx:
status: Triaged → Fix Released
Revision history for this message
Ghada Khalil (gkhalil) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.