search

redhat-developer / odo-init-image

ODO v3 no loner users this image!!! (Container for ODO v2 to setup SupervisorD inside S2I builder image.)
Apache License 2.0
7 stars 27 forks source link

support multi arch build of odo-init-image #49

Closed jichenjc closed 3 years ago

jichenjc commented 4 years ago

https://access.redhat.com/containers/?tab=overview#/registry.access.redhat.com/openshiftdo/odo-init-image-rhel7 mentioned it's only support x86 but not other arch

do we have any plan before that this will be supported for IBM z arch or power arch? as you can see odo which is highly relied by other dev tools rely on odo-init-image to init

kadel commented 4 years ago

The plan is actually moving away from using odo-init-image. Everything that we are building around Devfiles (https://github.com/openshift/odo/labels/area%2Fdevfile) is not going to require odo-init-image anymore.

jichenjc commented 4 years ago

@kadel thanks a lot for the info, will take a look at that but before that devfile ready to be working, this odo-init-image still needed?

do we have a forecast that start from when the odo-init-image is not needed anymore? thanks

jichenjc commented 4 years ago

@kadel can I know the plan of using devfiles? e.g openshift 4.4 , 4.5 etc?

kadel commented 4 years ago

@kadel can I know the plan of using devfiles? e.g openshift 4.4 , 4.5 etc?

sorry for the late reply, I might already mention that somewhere else. odo is already using devfiles, you just need to enable the experimental mode odo preference set experimental true. Devfiles should "graduate" out of the experimental around OCP 4.5 timeframe, that is the current plan, it will depend on how fast we can stabilize it"

sarveshtamba commented 4 years ago

@kadel @jichenjc just saw this issue and related it to https://github.com/openshift/odo-init-image/issues/63 I need to build odo-init-image for/on PowerPC64LE, so as to carry out Deploying a devfile using odo However as per above comments seems odo-init-image is going to be phased out gradually. Till then how does one carry out Deploying a devfile using odo on ppc64le? Considering the issues I have mentioned in https://github.com/openshift/odo-init-image/issues/63

PS:- I already set odo preference set experimental true and was trying to use Devfiles until I realized I will need odo-init-image built for/on powerpc64le.

jichenjc commented 4 years ago

@sarveshtamba what we are doing is re-build the image on our own arch (s390x) and use the new image to do the test @zhengxm123 can you help to provide additional info here?

sarveshtamba commented 4 years ago

@sarveshtamba what we are doing is re-build the image on our own arch (s390x) and use the new image to do the test @zhengxm123 can you help to provide additional info here?

@jichenjc I am trying to re-build the image on ppc64le power arch to use the new image to do the test, however facing the issues as mentioned in https://github.com/openshift/odo-init-image/issues/63 Any suggestions/inputs would be highly appreciated.

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/odo-init-image/issues/49#issuecomment-749240055): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.