sail up fails #481
Comments
|
I don't know what to say? Everything runs fine for me. I deleted all containers and images on my system and things still install properly. |
|
@driesvints Maybe the next step would be to compare hardware and figure this out, rather than straight up closing? People have been reporting this, I'm not sure you're only using your hardware as reference. |
|
I need a tangible way to reproduce this otherwise I cannot help. |
|
Can confirm, I too have hit a similar error. Interestingly enough, changing the base image from Ubuntu 21.04 to 22.04 in the docker/8.1/Dockerfile got past the first part. However, I then run into this beauty: Just when I finally had the schedule open up to take my team to sail too :/ |
|
From what I can looks like this could be due to source list corruption? https://askubuntu.com/questions/1385440/ubuntu-sudo-apt-get-update-404-not-found-problem |
|
I might be wrong on this, but looks like Ubuntu 21.04 EOL'd? |
|
|
@GoodM4ven Sorry to offend, first and last time trying to do anything on GitHub for me apparently. Didn't realize the Laravel community was so harsh to new people. Figure it out yourself then, cause according to @driesvints there is no issue and the rest of use are just up in the night. I'll stop the hour I have put into this and reconsider the Laravel ecosystem entirely. |
|
!EDIT! For posterity sake (@driesvints I am really really really sorry about another post but I figured it will save you closing a ton more issues over it) for those who are using this: For me default install using If you change your composer require so that it at least requires the version that was introduced or higher, then reinstall/update packages it will work. I am really lazy (new) and so So sorry to have annoyed everyone, I will never speak again, this last message was just really important to update so that the real fix was in there and not my work around below. Again really, really, really sorry I have never used Github for anything but myself during college for storing school projects on. I don't know etiquette or culture on here, and I sure don't know a lot about programming, and I am really sorry I dared to even try to be helpful. I will now go jump off a cliff that many here would like for me to do. Original message below:
I'd do a PR but I annoyed everyone and am useless and know nothing.. and honestIy I've never done a PR before on github/open source projects and don't know how they work -_- Sorry for being a useless piece of human garbage @GoodM4ven |
|
@driesvints So, many people report the same problem, but this particular problem isn't happening on your end. Instead of collecting data to help reproduce the problem, your reaction is to close issues and refuse to further investigate. This doesn't seem right. Can you reconsider your decision and open the issue up for discussion? Maybe you can't help, but others can. Isn't that the whole point of OSS? |
|
I can confirm that I also have had this issue a couple of months ago. I think we might have to change all the Dockerfile's to |
|
I see you are all still using Ubuntu 21.04 for PHP 8.1. You'll need to update that to 22.04: https://github.com/laravel/sail/blob/1.x/runtimes/8.1/Dockerfile#L1 For PHP 8.0 and 7.4 you need to stick to 20.04 because of some packages not being available on 22.04: https://github.com/laravel/sail/blob/1.x/runtimes/8.0/Dockerfile#L1 |
@dugajean we don't keep issues open which we can't replicate. People can still reply. The issue isn't locked. |
|
In general it's a good idea to keep the Dockerfiles up to date with what's changing in Sail. |
|
I had the same issue. My guess is that ubuntu 21.04 - has expired support and so some update sources are no longer available. The reason why it still works for some might be that the required files are still cached for them somewhere. my solution to this issue (for laravel 7.4, sail version v1.16.0): - (not tested for laravel 8.0 might work if the dockerfile for the runtime 8.0 is changed) modify the first line of the file ubuntu 20.04 is older but an LTS so updates should be available for longer ... this change alone produced an error: this error was solved by adding the following lines to the .env file: |
|
Yes, the problem seems to be related to runtime for PHP 7.4 and 8.0 which uses the image ubuntu:20.04. Runtime for PHP 8.1 use ubuntu:22.04 that seems to work fine. |
|
Same issue when installing the dependencies for an existing application using the docker image laravelsail/php81-composer. As per the latest documentation |
|
I tried with PHP 8.0 (default option when generating Laravel with sail) and ubuntu:20.04. Then change to PHP 8.1 with ubuntu 22.04 (default from its Dockerfile). Still got error like this: This issue gives me headache |
|
I had a similar problem using Laravel 9,2 and Sail 1.0.1 This is how I fixed it:
That worked for me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
On a fresh run in my system, when I run
vendor/bin/sail upI get the following error:It appears that this is a common occurrence, but all the tickets reporting the same bug have been closed. Before closing this ticket, can you please give it a look and confirm this is an actual bug?
Steps To Reproduce:
vendor/bin/sail upThe text was updated successfully, but these errors were encountered: