search

containers / podman-desktop

Podman Desktop is the best free and open source tool to work with Containers and Kubernetes for developers. Get an intuitive and user-friendly interface to effortlessly build, manage, and deploy containers and Kubernetes — all from your desktop.
https://podman-desktop.io
Apache License 2.0
4.62k stars 294 forks source link

Podman desktop - Unable to install compose #8483

Open siddhartharoy opened 1 month ago

siddhartharoy commented 1 month ago

Bug description

I am trying to install podman compose from podman desktop. But it fails to download. Have the same error with 1.11.1 and 1.12.0 both. This is a new laptop and Docker is not installed

OS - MacBook Pro M3 - Sonoma 14.6.1

Operating system

MacBook Pro M3 - Sonoma 14.6.1

Installation Method

Other

Version

1.12.0

Steps to reproduce

1) Installed Podman desktop using - podman-desktop-1.12.0-arm64.dmg. Also tried with universal installer but same issue 2) Went to settings and tried to install compose but it fails to download and install 3) Installing with admin privileges failed1 failed2

Relevant log output

Detailed logs and software versions are shown as an attachments in additional context section

Additional context

Logs podman logs

Versions versions1

odockal commented 1 month ago

@siddhartharoy Hello. thanks for opening the issue. I have seen the similar problem on Mac OS 14 with M2 chip. Although, it worked for compose, it did not work for kubectl. I believe that the cause is the same. Error seems bit different, but still similar. I suspect this one to blame: [compose] GET /repos/docker/compose/releases/assets/181338715 - 500 with id UNKNOWN in 940 ms In my case, I got this one: [kubectl-cli] GET /repos/kubernetes/kubernetes/releases?per_page=10 - 403 with id xxxx-yyyy.

Then the last error as seen in your screenshot is the same, object could not be cloned.

I think that problem was for you that github might have had an outage or in my case it was hitting a rate limit for requesting some information/files from github via its api.

odockal commented 1 month ago

@siddhartharoy Probably, if you try again, it might work. In cases of http code 500, might be also that you cannot reach github api endpoint? Might there be any proxy preventing you contacting such urls?

siddhartharoy commented 1 month ago

Hi @odockal, Thank you for the response. I tried multiple times but have same issue. I even at different hours but no success.

siddhartharoy commented 1 month ago

@siddhartharoy Probably, if you try again, it might work. In cases of http code 500, might be also that you cannot reach github api endpoint? Might there be any proxy preventing you contacting such urls?

No, there is no proxy

cdrage commented 2 weeks ago

@siddhartharoy @odockal

Tried this again locally and was unable to re-produce.

I was able to successfully install (and not receive any 500 or 403 error) with Compose.

I also uninstalled kubectl and kind and tried the same thing with those binaries, and had no issue.

Let me know @siddhartharoy if you can try again and see if the issue resolved.

akrueger commented 1 week ago

I have a similar issue. I cannot install kubectl or compose from Desktop:

Apple M1 Max Sonoma 14.6.1 (23G93)

Screenshot 2024-09-11 at 12 12 32 Screenshot 2024-09-11 at 12 12 57
benoitf commented 1 week ago

@akrueger could you check if /usr/local/bin folder exists ?

akrueger commented 1 week ago

@benoitf yes, it does and it is on the PATH

I manually added kubectl using this method and it works: https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/

Not sure where Podman Desktop is running into trouble. Are there logs I can check?

I haven't tried adding compose manually yet.

akrueger commented 1 week ago

@benoitf After playing around with it, I believe this happens when there are already symlinks in the bin folder for previous compose items (from Docker Desktop for example). Once I cleaned up Symlink there, it installed fine.

slemeur commented 1 week ago

linking to https://github.com/containers/podman-desktop/issues/5334#issuecomment-2345487340

cdrage commented 1 week ago

I think that we should add this to documentation under troubleshooting for Compose to check the system for symlinks, what do you think @slemeur @benoitf ?

Looks like fallout from uninstalling docker desktop / installing compose may create issues with regards to the symlinking.

benoitf commented 1 week ago

troubleshooting doc is great but Podman Desktop should detect that there is a symlink if there is a symlink we could ask the user to replace it, etc.

so no error -1, just questions being asked by the user

akrueger commented 5 days ago

@benoitf @cdrage Would it work to namespace it such as Docker Desktop has done here with kubectl?

Screenshot 2024-09-16 at 14 11 32

I think it's reasonable to assume Docker reserves the docker-compose command for itself. In fact if you install Docker Desktop after Podman Desktop it's just going to overwrite that symlink with its own for docker-compose.

docker-compose.podman seems like a good option

simonmacor commented 4 days ago

I'm facing the same problem.

Operating system Windows 10

version 1.12.0

cdrage commented 4 days ago

I'm facing the same problem.

Operating system Windows 10

version 1.12.0

Any way you can provide logs from Podman Desktop / errors that you get? As you are the first coming from Windows with this issue.

simonmacor commented 4 days ago
compose setup logs
cdrage commented 4 days ago

compose setup logs

Could you do whereis docker-compose on Powershell and show where your docker-compose currently is?

simonmacor commented 4 days ago

docker-compose is not installed

cdrage commented 4 days ago

compose setup logs

if it does not show docker-compose existing when you do whereis, it could either be:

Could you double check you have nothing in your proxy settings / no VPN and try again?

simonmacor commented 4 days ago

Sorry for the lack of details. I already checked the VPN settings. I don't have a vpn configured.

neverd1m commented 2 days ago

I've faced similar issue with both kubectl and compose installation. Following the thread i tried to change my network presence and use VPN. It did work after that, so i assume the idea of github having limits is correct.

@siddhartharoy Hello. thanks for opening the issue. I have seen the similar problem on Mac OS 14 with M2 chip. Although, it worked for compose, it did not work for kubectl. I believe that the cause is the same. Error seems bit different, but still similar. I suspect this one to blame: [compose] GET /repos/docker/compose/releases/assets/181338715 - 500 with id UNKNOWN in 940 ms In my case, I got this one: [kubectl-cli] GET /repos/kubernetes/kubernetes/releases?per_page=10 - 403 with id xxxx-yyyy.

Then the last error as seen in your screenshot is the same, object could not be cloned.

I think that problem was for you that github might have had an outage or in my case it was hitting a rate limit for requesting some information/files from github via its api.

cdrage commented 2 days ago

With the limit: "In general, no more than 80 content-generating requests per minute and no more than 500 content-generating requests per hour are allowed. "

It could be that the limit is being reached before Podman Desktop checks due to limiting per IP.

z-aki commented 1 day ago

using a VPN / proxy

In my case it was a VPN with a custom CA certificate that podman desktop did not like. Is there a way for podman to use macOS Keychain certificates? VSCode does that. Browsers also do it.