Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error when installing compose system wide on ubuntu #4456

Closed
lstocchi opened this issue Oct 20, 2023 · 2 comments · Fixed by #4502
Closed

Error when installing compose system wide on ubuntu #4456

lstocchi opened this issue Oct 20, 2023 · 2 comments · Fixed by #4502
Assignees
@benoitf
Labels
area/extensions/compose 🎹 kind/bug 🐞 Something isn't working sprint/unplanned theme/compose
Milestone
1.5.0

Comments

@lstocchi
Copy link
Contributor

Bug description

error_onboarding_compose

Operating system

Ubuntu 22.04

Installation Method

Installer from website/GitHub releases

Version

next (development version)

Steps to reproduce

No response

Relevant log output

No response

Additional context

No response
@lstocchi lstocchi added the kind/bug 🐞 Something isn't working label Oct 20, 2023
@cdrage
Copy link
Contributor

cdrage commented Oct 21, 2023

Any output from the dev console?

@odockal
Copy link
Contributor

odockal commented Oct 23, 2023

@cdrage erros from dev console:

VM5:2 main ↪️ [compose] Failed to install 'docker-compose' binary: Command execution failed with exit code 127: Command execution failed with exit code 127
console.<computed> @ VM5:2
(anonymous) @ VM5:2
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2

VM5:2 main ↪️ [compose] Command execution failed with exit code 127: Command execution failed with exit code 127
    at ChildProcess.<anonymous> (/home/odockal/git/podman-desktop/dist/linux-unpacked/resources/app/packages/main/dist/index.cjs:382:12995)
    at ChildProcess.emit (node:events:514:28)
    at Process.onexit (node:internal/child_process:291:12)
console.<computed> @ VM5:2
(anonymous) @ VM5:2
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2

cdrage added a commit to cdrage/podman-desktop that referenced this issue Oct 23, 2023
@cdrage
nit: disable compose onboarding for linux
02d1467 
### What does this PR do?

Disables showing onboarding / enablement for Linux until we have fixed
the issue: containers#4456

### Screenshot/screencast of this PR

<!-- Please include a screenshot or a screencast
explaining what is doing this PR -->

N/A, it will not appear when running on Linux

### What issues does this PR fix or reference?

<!-- Include any related issues from Podman Desktop
repository (or from another issue tracker). -->

Closes containers#4475

### How to test this PR?

<!-- Please explain steps to reproduce -->

Run yarn watch on Linux, you will not see the enablement button.

If you run it on Windows / Mac it will show.

Signed-off-by: Charlie Drage <charlie@charliedrage.com>
This was referenced Oct 23, 2023
Closed
Closed
cdrage added a commit to cdrage/podman-desktop that referenced this issue Oct 24, 2023
@cdrage
refactor: updated compose onboarding installation
60fc773 
### What does this PR do?

* Installation is now Download which is more correct and files updated
  (installation.ts now download.ts)
* Onboarding compose process is more flowing and streamlined, the
  system-wide install is now it's own step as it's required for
  onboarding
* Updated documentation on how to use compose within the onboarding
  process
* Disables onboarding for Linux as it is broken right now by
containers#4456

### Screenshot/screencast of this PR

<!-- Please include a screenshot or a screencast
explaining what is doing this PR -->

### What issues does this PR fix or reference?

<!-- Include any related issues from Podman Desktop
repository (or from another issue tracker). -->

Closes containers#4475
Closes containers#4476

### How to test this PR?

Go through the onboarding process on a non-linux machine. If you are on
a linux machine, you should NOT see the setup button anymore.

<!-- Please explain steps to reproduce -->
@cdrage cdrage mentioned this issue Oct 24, 2023
Merged
cdrage added a commit to cdrage/podman-desktop that referenced this issue Oct 24, 2023
@cdrage
refactor: updated compose onboarding installation
92c7f34 
### What does this PR do?

* Installation is now Download which is more correct and files updated
  (installation.ts now download.ts)
* Onboarding compose process is more flowing and streamlined, the
  system-wide install is now it's own step as it's required for
  onboarding
* Updated documentation on how to use compose within the onboarding
  process
* Disables onboarding for Linux as it is broken right now by
containers#4456

### Screenshot/screencast of this PR

<!-- Please include a screenshot or a screencast
explaining what is doing this PR -->

### What issues does this PR fix or reference?

<!-- Include any related issues from Podman Desktop
repository (or from another issue tracker). -->

Closes containers#4475
Closes containers#4476

### How to test this PR?

Go through the onboarding process on a non-linux machine. If you are on
a linux machine, you should NOT see the setup button anymore.

<!-- Please explain steps to reproduce -->
cdrage added a commit to cdrage/podman-desktop that referenced this issue Oct 24, 2023
@cdrage
refactor: updated compose onboarding installation
694410f 
### What does this PR do?

* Installation is now Download which is more correct and files updated
  (installation.ts now download.ts)
* Onboarding compose process is more flowing and streamlined, the
  system-wide install is now it's own step as it's required for
  onboarding
* Updated documentation on how to use compose within the onboarding
  process
* Disables onboarding for Linux as it is broken right now by
containers#4456

### Screenshot/screencast of this PR

<!-- Please include a screenshot or a screencast
explaining what is doing this PR -->

### What issues does this PR fix or reference?

<!-- Include any related issues from Podman Desktop
repository (or from another issue tracker). -->

Closes containers#4475
Closes containers#4476

### How to test this PR?

Go through the onboarding process on a non-linux machine. If you are on
a linux machine, you should NOT see the setup button anymore.

<!-- Please explain steps to reproduce -->

Signed-off-by: Charlie Drage <charlie@charliedrage.com>
@benoitf benoitf self-assigned this Oct 24, 2023
benoitf added a commit to benoitf/desktop that referenced this issue Oct 24, 2023
@benoitf
fix: handle flatpak usecase for admin commands
2721b04 
we need to use flatpak-spawn only after command is set and not at the beginning

else we may try to execute commands with incorrect order of params

related to containers#4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
benoitf added a commit to benoitf/desktop that referenced this issue Oct 24, 2023
@benoitf
fix: use bash -c because when using with flatpak-spawn it does not work
6039ab0 
fixes containers#4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
This was referenced Oct 24, 2023
Merged
Merged
benoitf added a commit that referenced this issue Oct 25, 2023
@benoitf
fix: handle flatpak usecase for admin commands
dd85d75 
we need to use flatpak-spawn only after command is set and not at the beginning

else we may try to execute commands with incorrect order of params

related to #4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
benoitf added a commit that referenced this issue Oct 25, 2023
@benoitf
fix: use bash -c because when using with flatpak-spawn it does not work
7ff0282 
fixes #4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
benoitf added a commit to benoitf/desktop that referenced this issue Oct 25, 2023
@benoitf
fix: use bash -c because when using with flatpak-spawn it does not work
58b364c 
fixes containers#4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
benoitf added a commit to benoitf/desktop that referenced this issue Oct 25, 2023
@benoitf
fix: handle flatpak usecase for admin commands
45991a6 
we need to use flatpak-spawn only after command is set and not at the beginning

else we may try to execute commands with incorrect order of params

related to containers#4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
@benoitf benoitf added this to the 1.5.0 milestone Oct 25, 2023
benoitf added a commit that referenced this issue Oct 25, 2023
@benoitf
fix: use bash -c because when using with flatpak-spawn it does not work
40d70cb 
fixes #4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
benoitf added a commit that referenced this issue Oct 25, 2023
@benoitf
fix: handle flatpak usecase for admin commands
1dd4e17 
we need to use flatpak-spawn only after command is set and not at the beginning

else we may try to execute commands with incorrect order of params

related to #4456

Signed-off-by: Florent Benoit <fbenoit@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benoitf benoitf

Labels
area/extensions/compose 🎹 kind/bug 🐞 Something isn't working sprint/unplanned theme/compose
Projects
Podman Desktop Planning
Archived in project
Milestone
1.5.0
Development

Successfully merging a pull request may close this issue.

fix: use bash -c because when using with flatpak-spawn it does not work benoitf/desktop
6 participants
@benoitf @jeffmaury @cdrage @odockal @lstocchi @podman-desktop-bot