docker-magento
docker-magento copied to clipboard
One code setup can't access to bin/magento
Description I tried setup magento 2.4.3-p1 version and i get this error when download the files: bin/magento no such file or directory
Expected Result download magento's files
Actual Result bin/magento no such file or directory
I can confirm what @NecmiGorkemKivanc has found!
Steps to reproduce:
curl -s https://raw.githubusercontent.com/markshust/docker-magento/master/lib/template | bash
bin/download 2.4.2
bin/setup magento.local
I have downloaded the version 2.4.2 and I get the same problem issue.Seems that the Magento is not downloaded correctly.
After dowloading of Magento 2.4.2 I have executed the bin/setup command and I have found an error:
chmod: cannot access 'bin/magento': No such file or directory
Update: After testing another version like the 2.4.4 all the magento modules are downloaded and it creates a src folder.. All works as well. It seems to me a problem with the specific old versions.
@markshust Could you please help us?
thanks
Hey @shinesoftware, if you need fastly resolve you can try to manual setup. It's worked for me.(Installed already exist project)
Hi @NecmiGorkemKivanc, yes thanks! I am trying to setup it manually but I'd like to improve this tool! I'd like to use it for my new / old Magento project.
This issue is still happening, has anybody written a fix for it yet?
@jsjsvsvs I thing that we need a little help from @markshust
@NecmiGorkemKivanc Which manual setup are you referring too? Manual Step > New Projects fails as well with bin/magento command not found. Same issue
I have the same issue when try to setup Magento 2.4.3-p3 with manual instructions during bin/setup command:
chmod: cannot access 'bin/magento': No such file or directory
UPD: but when try to install 2.4.5 or 2.4.5-p1 all work smoothly.
I'm willing to take in a PR that fixes this, but given that 2.3 reached EOL in September, and 2.4.3 reaches EOL in a little over a month, I have little motivation to fix these versions.
I tagged this with a "help wanted" flag. If there isn't a corresponding PR to fix this by Nov 28 (EOL noted at https://experienceleague.adobe.com/docs/commerce-operations/release/planning/lifecycle-policy.html), I'll automatically close out this ticket as "will not fix".
I have the same issue when try to setup Magento 2.4.3-p3 with manual instructions during
bin/setupcommand:chmod: cannot access 'bin/magento': No such file or directoryUPD: but when try to install 2.4.5 or 2.4.5-p1 all work smoothly.
v2.4.4 and v2.4.5-p1 both broken for me using the one-line setup script (brand new user of this project) so it doesn't seem to be just old versions that have this problem
2.4.3 is official end-of-life tomorrow (aka DEAD) so I won't be supporting it anymore, and will be proactively closing out this ticket as wontfix.
I just installed 2.4.5-p1 and the install went fine, so if you are having issues please open another ticket with full details (operating system, Docker version, exactly steps you are doing, etc.) and I'll check it out 👍
I struggled with this chmod error trying to install an older version (2.4.3-p3) for working with a legacy project.
The issue was that magento includes some composer plugins that need to be enabled, but the composer create-project command is called using bin/clinotty which is non-interactive. Because of this composer assumes there is no permissions to enable the plugin, and the install does not complete successfully (but there is no apparent error).
The solution is to edit bin/download and change the relevant line (depending on edition you are installing) from bin/clinotty to bin/cli.
Then answer questions like this with y
Do you trust "magento/magento-composer-installer" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?] y