-
-
Notifications
You must be signed in to change notification settings - Fork 981
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
chmod: cannot access 'bin/magento': No such file or directory #731
Comments
Work-around on WSL 2 Ubuntu for me.
|
Cheers for this. I had this issue too, and this seemed to work. To clarify it a bit so that others running into this issue might use it: For your first command, replace With your second command you essentially re-clone the magento install into here, I ran into issues that the folder wasn;t empty so I created a new directory ( |
Thanks for posting this info. I'll try to finally do an install of docker-magento on Linux after I tag & publish the next version to make sure the README is still correct. Definitely willing to take in any updates to it if needed. |
Thanks Mark, if you could drop a message here when the next version is up, perhaps I can try it on weekend :) |
Reproducing bug for 2.4.3-p2 with |
@myselfhimself can you please post your full operating system & host details? Everything works fine for me on macOS, so it'll be very hard/impossible to confirm this is even an issue without all of the debugging details. |
@markshust I moved to the 2.4.4 install myself because that works fine out of the box - but I believe there is something off when loading Magento into the docker file, possibly related to permission errors that are not reproducable on macOS, as read here. For me this happened on Ubuntu 22.04 LTS, fresh install. |
Thanks! I have limited time coming up, but will definitely accept any PRs related to this issue. |
|
Reproduced bug again, but managed to reproduce fix #731 (comment) by @LiamKarlMitchell |
Are there any errors occurring when running |
See attachment |
@myselfhimself appreciate it. It appears this issue is related to Composer:
...and can be solved with: https://magento.stackexchange.com/questions/352353/why-composer-install-is-asking-to-allow-plugins So, I think we just need to update the Linux README to include this step in the process? If someone on Linux can verify it, that would be extremely helpful. Here's a link to the Linux part of the readme: https://github.com/markshust/docker-magento#linux |
Obviously the fix was added in Magento 2.4.4 dev in January 2022 per this issue... Since I am trying to install Magento 2.4.3-p2 for stability reasons with a given set of modules... this would mean that the oneliner be corrected or to resort to a manual install with some manual change between some command line. That manual change could indeed be listed in the docker-magento readme. Will look into it to contribute a README patch tomorrow hopefully. |
@markshust The wise paths to fix in order to keep the docker-magento oneliner install script mostly automated would be to ask Magento 2's upstream project to add that composer.json fix to Magento <2.4.4 releases (asking now) or to induce the |
@markshust On the non-interactive
Would you see this fit for adding to the docker-magento one-liner ? |
@myselfhimself absolutely, thanks so much for the lines! That made it easy for me. This shouldn't adversely affect any version of M2. Can you confirm that it works now? |
@markshust Thanks for that patching! Those lines should ideally be run before the composer create-project downloading call in the docker-magento/compose/bin/download Line 24 in f81cfc4
while you have put them in the bin/setup script, which runs after bin/download in the onlinesetup script
I will test your PR tomorrow anyways, I may be mistaken in that too-late placement assumption. |
…r all magento <2.4.4
Just proposed a PR will the 3 lines located in #741 seems to a duplicate of this. Asked submitter to try out that PR. Will try it out too on a faster computer... |
@markshust The PR needs your approval to run Github Actions tests |
You'll probably best add the I think in the way suggested with myselfhimself@6a2fb7e, it won't work. Also see composer/composer#10928 (comment) I would strongly suggest to only apply these changes for Magento versions >= 2.3.7 and < 2.4.4 if that's possible, reasons:
|
@hostep Thank you, I improved the PR with your 3-steps suggestion (composer create project with no-install flag, add 3 allowances for magento-related dependencies, composer install fully) We could either integrate the >= 2.3.7 to < 2.4.4 filter in that PR or a new one, once the current PR is merge. |
To me the PR is OK, tested manually locally (using the github CLI tool named
|
Thanks or your response @myselfhimself I'm getting an error trying to checkout 742 ❯ gh pr checkout 742 Also, getting an error (without checkout?) while running bin/setup chmod: cannot access 'bin/magento': No such file or directory |
Apologies, I just added a |
I believe I may be getting the same error (but there might be a step that is incorrect) docker-magento73126072000_b on master [?] took 2s docker-magento73126072000_b on master [?] [InvalidArgumentException] create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--ask] [--] [] [] [] docker-magento73126072000_b on master [?] took 21s |
You should stop your previously created running docker images between attempts (so, basically now) with: Also each new attempt would need a new directory.. |
…ugin allowances
@hostep I added version filtering to the PR as you recommended. Needs testing. |
is there any news? when i try to install 2.3.4 i receive this error and nothing happens after that `docker exec -it d7124a76465cca995dee2bcc7eaa68dfce124a6029b80a004aeb7554ea0f7364 /bin/sh
Problem 1 |
I resolved this issue with adding these lines the on bin/download file;
|
I tried all of your methods but still got this error: `Creating a "magento/project-community-edition=2.4.4" project at "./" [InvalidArgumentException] create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--ask] [--] [] [] [] Composer could not find a composer.json file in /var/www/html I have reinstalled from fresh many times. System: Debian 8 GB ram. |
@nhapq I think you should clear all content in your container(/var/www/html). |
Is Magento version 2.3.4 still supported by you? I have seen that support for php 7.3 has been removed. |
I don't necessarily support specific versions of Magento anymore, but moreso the underlying PHP versions. 7.3 reached EOL a while ago, so that support was dropped. 7.4 support will be dropped at the end of November, leaving only 8.1 (and probably 8.2 at that time). @nhapq any error "Project directory "/var/www/html/." is not empty." means the directory is not empty, so it needs to be fully purged before trying to re-execute the install as @anilacikgoz pointed out. You can do this with I believe this issue about composer allow-plugins was already fixed a while ago? If not, please let me know. |
Also experiencing this issue when installing 2.4.3-p1 community, I will add those to my scripts, which i keep in version control after the initial docker-compose template clone. Any plan to fix it in this project? |
Magento 2.4.3 officially hits end-of-life tomorrow, so I'll be closing this out as "won't fix". PHP 7 image will also get deprecated (meaning you can use it, but I won't be taking any updates in). When something reaches end-of-life, it's dead and needs to stop being used ASAP! I don't plan on supporting anything that is already buried in a coffin 😁 |
Not helped :( [InvalidArgumentException] |
Composer auth has already been set up. [InvalidArgumentException] |
Everything is working properly, so unable to replicate. Your error is leading to artifacts being left over from a preexisting install attempt. Please see markshust/docker-magento#install-fails-because-project-directory-is-not-empty |
@markshust Yes I do not use credentials from this portal https://marketplace.magento.com/ 487/487 [============================] 100% |
osony@C02F45AFMD6P magento % bin/setup @markshust What I missed? |
Your install probably failed at some point. Please see https://github.com/markshust/docker-magento#install-fails-because-project-directory-is-not-empty |
When installing Magent0 2.4.3 p1
setup like bin/setup magento.test
it showing this error
The text was updated successfully, but these errors were encountered: