https://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-07-02T14:59:46ZPulpPulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=453212019-07-02T14:59:46Zdaviddavis
<ul><li><strong>Parent issue</strong> changed from <i>#5004</i> to <i>#5069</i></li></ul> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=453332019-07-02T21:17:49Zmdepaulo@redhat.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>I reworked them, but still need to figure out naming conventions and stable interfaces for CMDs/ENTRYPOINTs.</p>
<p><a href="https://github.com/mikedep333/pulpcore/tree/1-image-to-rule-them-all" class="external">https://github.com/mikedep333/pulpcore/tree/1-image-to-rule-them-all</a></p> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=453722019-07-03T19:16:26Zmdepaulo@redhat.com
<ul></ul><p>Status Update:</p>
<p>I've done more research, including discussion with #podman on Freenode.</p>
<p>I've decided to keep the current common entrypoint in the Dockerfile, and use the commands that we're currently using, but with the /usr/bin/ dropped:<br>
pulp-api<br>
pulp-content<br>
pulp-resource-manager<br>
pulp-worker</p>
<p>These are the same as the systemd service names.</p>
<p>The entrypoint can always take special steps based on the command passed to it.</p>
<p>Alternatives considered:<br>
1. Use a label like ROLE=pulp-api (This has the disadvantage of being less straightforward than specifying the command. The command is still like a role.)<br>
2. Use a podman runlabel (No Docker support, and would only work for a single container/process/service anyway.)<br>
3. `podman play kube` (No docker support, and the stable command API would be valuable for users that never see updated kube .yml file, but run the "latest" image. Still, I might use this instead of a script to launch all 4 containers.)<br>
4. `docker compose` (Same as above, except Docker proprietary.)<br>
5. All processes in 1 container - Not how containers are supposed to be used, and prevents auto-scaling done by K8s.</p>
<p>TODO: Update pulp-operator for this</p> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=454552019-07-08T12:48:33Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li></ul> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=455452019-07-10T20:32:23ZAnonymous
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Collapse 4 container images into 1. They will be used as 4+ different containers by specifying d..." href="https://pulp.plan.io/projects/pulp/repository/pulpcore/revisions/82c56514d66b3e77a9aaca46bb98d3f242f54c8f">pulpcore|82c56514d66b3e77a9aaca46bb98d3f242f54c8f</a>.</p> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=463992019-08-07T16:26:13Zmdepaulo@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Task #5060: Rework 4 existing container images into 1 image with 4 different entrypointshttps://pulp.plan.io/issues/5060?journal_id=472052019-09-03T17:38:26Zmdepaulo@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - COMPLETE</i></li></ul>