-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
odo is failing when devfile container component defines command
#5620
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/Critical
We need to stop doing everything and fix this ASAP. It is making the project unusable.
Comments
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Apr 7, 2022
…ents This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Apr 7, 2022
…ents This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Apr 7, 2022
…ents This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] redhat-developer#5620
This was referenced Apr 7, 2022
3 tasks
3 tasks
openshift-merge-robot
pushed a commit
that referenced
this issue
Apr 8, 2022
…ntainer components (#5640) * Reproduce the issue via a test case with `odo push` * Always ignore `command` and `args` fields in Devfile container components This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] #5620
openshift-merge-robot
pushed a commit
that referenced
this issue
Apr 8, 2022
…ner components (#5639) * Reproduce the issue via a test case with `odo dev` * Always ignore `command` and `args` fields in Devfile container components This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] #5620
Repository owner
moved this from For Review
to Done
in odo v3-beta1
Apr 8, 2022
rm3l
added a commit
to rm3l/odo
that referenced
this issue
May 27, 2022
Otherwise, the default images used spwan containers that terminate right away, which would prevent us from using the new '--no-supervisord' flag. This has no impact when running with Supervisord, because [1] introduced a workaround this that always overrides the container entrypoint. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
May 30, 2022
Otherwise, the default images used spwan containers that terminate right away, which would prevent us from using the new '--no-supervisord' flag. This has no impact when running with Supervisord, because [1] introduced a workaround this that always overrides the container entrypoint. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
May 31, 2022
Otherwise, the default images used spwan containers that terminate right away, which would prevent us from using the new '--no-supervisord' flag. This has no impact when running with Supervisord, because [1] introduced a workaround this that always overrides the container entrypoint. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
May 31, 2022
Otherwise, the default images used spwan containers that terminate right away, which would prevent us from using the new '--no-supervisord' flag. This has no impact when running with Supervisord, because [1] introduced a workaround this that always overrides the container entrypoint. [1] redhat-developer#5620
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Jun 3, 2022
Otherwise, the default images used spwan containers that terminate right away, which would prevent us from using the new '--no-supervisord' flag. This has no impact when running with Supervisord, because [1] introduced a workaround this that always overrides the container entrypoint. [1] redhat-developer#5620
cdrage
pushed a commit
to cdrage/odo
that referenced
this issue
Aug 31, 2022
…ner components (redhat-developer#5639) * Reproduce the issue via a test case with `odo dev` * Always ignore `command` and `args` fields in Devfile container components This is a hotfix for [1], until a proper fix is implemented, which would consist in keeping using supervisord as pid1, and executing the command with args "on the side" as a separate process. [1] redhat-developer#5620
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/Critical
We need to stop doing everything and fix this ASAP. It is making the project unusable.
devfile/registry#102 (comment)
Odo is not able to use devfiles that have
container
component with a customcommand
. Problem is that in the current odo implementation it overrides the default process in deployment which means that supervisord is not started. When supervisord is not running, odo is not able to execute any commands in the container.It needs to be backported into v2, and we have to release new v2 release.
A quick fix is for odo to ignore
command
andargs
fields in container components.The proper fix is going to be to keep using
supervisord
as pid1, and execute thecommmand
withargs
"on the side" as a separate process.Because this needs to be fixed ASAP, we will start with quick fix and than work on a proper fix once we are not pressured by time.
/kind bug
/priority high
The text was updated successfully, but these errors were encountered: