Level 28
Hope that will help you. https://laracasts.com/series/whats-new-in-laravel-8/episodes/12
Sep 13, 2021
4
Level 1
Mac BigSur -> Docker -> sail up -> laravel.test Error
I just downloaded Docker Desktop for Mac and am able to confirm the installation using the getting-started container. I then follow the instructions for downloading the build file using curl and letting it install the laravel directory. From there, I run the vendor/bin/sail up command. Everything starts Pulling except laravel.test, which comes back in red as: laravel.test error (not very descriptive).
Here are my steps:
- Open Terminal
- Run curl -s "https://laravel.build/myappname?with=pgsql,mailhog,selenium" | bash
- cd to myappname
- Run vendor/bin/sail up (I've also tried ./vendor/bin/sail up after scouring Google results)
- It begins to run the first time and that's when I get the above error
- If I just let it finish out it comes up. When I navigate to localhost, it shows the docker getting-started tutorial
- Just for fun I did sail down and sail up, just to see, and the same results
I have uninstalled and re-installed this many times with variations on what might fix it, including running it as sudo. I've looked through many help articles but no one seems to be having the specific problem that the laravel.test pulling errors out. I've tried, in vain, to find what is actually going on behind the scenes for the laravel.test pull, so I can check a URL directly or something, but I simply do not know enough of the background mechanics to trace it down.
Any help would be greatly appreciated. Side note, this is a fresh install for a new project, so not like I'm trying to do this in an existing project or repo.
Level 1
Thank you for the reply. Not really sure what in the link was supposed to be helpful so I consumed all of it. After watching the full video, I don't get any of the results he gets. The comments didn't have much that was super helpful. I did brew uninstall PHP, postgresql, MySQL, httpd, yarn, and a few others that looked like they may cause some issues but no dice. I'm attaching an output of what happens on a fresh install after I run vendor/bin/sail up:
EDIT: Looks like laracasts forums don't allow for uploading images. I threw the screenshot up on imgbb.com: it is https[colon]//ibb[dot]co/YLYFjQ1
Had to substitute some words in for the link. Replace [colon] with : and [dot] with . so that the link will work. I'm too new to post links at the moment (forum errors out).
Level 1
Update: I still have the same error. Same issues. Few things:
-
If I go to Docker Desktop -> Images and click Pull next to sail-8.0/app, it says Error 500 [https]://sail-8.0/v2/ Service Unavilable. Is this expected? (Leave out brackets. It tried to say it was a link and I'm still new/restricted)
-
localhost tries to take me to localhost/tutorial/ or localhost/getting-started. If I manually do localhost/index.php, I then get the Laravel welcome screen. Does this mean apache is somehow not configured correctly in the container? Or, perhaps, an env is not right?
Level 1
Added this .htaccess to the root folder (see below). After that, I restarted the sail server. If I go to localhost in my Chrome browser it still redirects to localhost/tutorial but with a 404 not found. If I do localhost/index.php it loads the Laravel page.
All of that said, if I open an incognito tab and go to localhost it loads the Laravel page with zero issues. I've tried clearing cookies and cache for localhost in Chrome, but it doesn't work. I suspect I'll need to clear browser-wide cookies and/or cache..but I'm not in the mood to be kicked out of everything. So, for now, I'll just use the incognito tab.
Options -MultiViewsRewriteEngine On
RewriteCond %{REQUEST_FILENAME} -d [OR] RewriteCond %{REQUEST_FILENAME} -f RewriteRule ^ ^$1 [N]
RewriteCond %{REQUEST_URI} (.\w+$) [NC] RewriteRule ^(.*)$ public/$1
RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ server.php
Please or to participate in this conversation.