fatal: destination path '.' already exists and is not an empty directory. exit status 128

[ericobreque]

Preconditions and environment

With the manual setup, it shows this error : fatal: destination path '.' already exists and is not an empty directory. exit status 128

In the step: bin/cli git clone git@github.com:magento/magento2.git .

Using ubuntu 24.04

Steps to reproduce

Expected result

.

Actual result

.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ericobreque. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[bhennesAdv]

Hello @ericobreque,

I might be mistaken but this issue is not related to magento at all, is it ?
The error you get is from the git clone command which does not allow an existing folder as a clone destination.

See https://gist.github.com/ZeroDragon/6707408 for example.
I don't get why you are using bin/cli ? What is this from ?
What manual setup are you talking about ? Any link to the documentation ?

See https://git-scm.com/docs/git-clone

NAME

git-clone - Clone a repository into a **new** directory

Kind Regards,
Baptiste

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@bhennesAdv Thanks for your Contribution!!

Hi @ericobreque,

Thanks for your reporting and collaboration.

Please refer this comment #39777 (comment) and let us know if you are still facing any issue.

Thanks.