Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-18998

(7.3.z) Chained s2i builder image with binary artifact is taking too much space

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.3.1.GA
    • 7.3.0.CD18, 7.3.0.GA
    • OpenShift
    • None
    • Hide 
      1. mvn test -Peap73-openjdk11 -Dxtf.test_properties.path=test.properties.os-ocp311 -Dxtf.eap.73-openjdk11.image=registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-openjdk11-openshift-rhel8:7.3.0-16 -Dtest=QuickstartsSmokeTest#batchProcessingTest

2. oc login https://master.multinode-nfs-022.dynamic.xpaas:8443/
3. oc registry login --skip-check
# oc expose service docker-registry --hostname=default-route-openshift-image-registry.apps.multinode-nfs-022.dynamic.xpaas -n default
4. podman login -u $(oc whoami) -p $(oc whoami -t) --tls-verify=false  docker-registry-default.apps.multinode-nfs-022.dynamic.xpaas
5. podman pull docker-registry-default.apps.multinode-nfs-022.dynamic.xpaas/73-openjdk11-4qf4/batch-processing-build-artifacts
6. pomdam images
7. dive --source=podman 103eb5d7f7c0
      Show
      1. mvn test -Peap73-openjdk11 -Dxtf.test_properties.path=test.properties.os-ocp311 -Dxtf.eap.73-openjdk11.image=registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-openjdk11-openshift-rhel8:7.3.0-16 -Dtest=QuickstartsSmokeTest#batchProcessingTest 2. oc login https: //master.multinode-nfs-022.dynamic.xpaas:8443/ 3. oc registry login --skip-check # oc expose service docker-registry --hostname= default -route-openshift-image-registry.apps.multinode-nfs-022.dynamic.xpaas -n default 4. podman login -u $(oc whoami) -p $(oc whoami -t) --tls-verify= false docker-registry- default .apps.multinode-nfs-022.dynamic.xpaas 5. podman pull docker-registry- default .apps.multinode-nfs-022.dynamic.xpaas/73-openjdk11-4qf4/batch-processing-build-artifacts 6. pomdam images 7. dive --source=podman 103eb5d7f7c0

      Instead of copying the server to /s2i-output/server we can:

      • we delete the deployments link from JBOSS_HOME/standalone/deployments
      • we copy the /deployments to JBOSS_HOME/standalone/
      • we create a link /s2i-output/server ==> JBOSS_HOME

        1. s2i-builder-image.png
          s2i-builder-image.png
          313 kB

            jdenise@redhat.com Jean Francois Denise
            jdenise@redhat.com Jean Francois Denise
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: