sail: sail up fails
- Sail Version: 1.3.18
- Laravel Version: 8.77
- PHP Version: 7.4
- Host operating system: macOS 12.15.1
Description:
On a fresh run in my system, when I run vendor/bin/sail up I get the following error:
composer start ✭
> vendor/bin/sail up -d
[+] Running 0/1
⠿ laravel.test Error 0.2s
[+] Building 9.0s (8/15)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/ubuntu:21.10 6.3s
=> [ 1/11] FROM docker.io/library/ubuntu:21.10@sha256:ff46b78279f207db3b8e57e20dee7cecef3567d09489369d80591f150f9c8154 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 99B 0.0s
=> CACHED [ 2/11] WORKDIR /var/www/html 0.0s
=> CACHED [ 3/11] RUN ln -snf /usr/share/zoneinfo/UTC /etc/localtime && echo UTC > /etc/timezone 0.0s
=> ERROR [ 4/11] RUN apt-get update && apt-get install -y gnupg gosu curl ca-certificates zip unzip git supervisor sqlite3 libcap2-bin libpng-dev python2 && mkdir -p ~/.gnupg && chmod 600 ~/.gnupg && echo "di 2.7s
------
> [ 4/11] RUN apt-get update && apt-get install -y gnupg gosu curl ca-certificates zip unzip git supervisor sqlite3 libcap2-bin libpng-dev python2 && mkdir -p ~/.gnupg && chmod 600 ~/.gnupg && echo "disable-ipv6" >> ~/.gnupg/dirmngr.conf && apt-key adv --homedir ~/.gnupg --keyserver hkps://keyserver.ubuntu.com --recv-keys 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C && echo "deb https://ppa.launchpadcontent.net/ondrej/php/ubuntu impish main" > /etc/apt/sources.list.d/ppa_ondrej_php.list && apt-get update && apt-get install -y php7.4-cli php7.4-dev php7.4-pgsql php7.4-sqlite3 php7.4-gd php7.4-curl php7.4-memcached php7.4-imap php7.4-mysql php7.4-mbstring php7.4-xml php7.4-zip php7.4-bcmath php7.4-soap php7.4-intl php7.4-readline php7.4-pcov php7.4-msgpack php7.4-igbinary php7.4-ldap php7.4-redis php7.4-xdebug && php -r "readfile('https://getcomposer.org/installer');" | php -- --install-dir=/usr/bin/ --filename=composer && curl -sL https://deb.nodesource.com/setup_16.x | bash - && apt-get install -y nodejs && npm install -g npm && curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - && echo "deb https://dl.yarnpkg.com/debian/ stable main" > /etc/apt/sources.list.d/yarn.list && apt-get update && apt-get install -y yarn && apt-get install -y mysql-client && apt-get install -y postgresql-client && apt-get -y autoremove && apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*:
#0 1.564 Ign:1 http://ports.ubuntu.com/ubuntu-ports impish InRelease
#0 1.713 Ign:2 http://ports.ubuntu.com/ubuntu-ports impish-updates InRelease
#0 1.867 Ign:3 http://ports.ubuntu.com/ubuntu-ports impish-backports InRelease
#0 2.021 Ign:4 http://ports.ubuntu.com/ubuntu-ports impish-security InRelease
#0 2.171 Err:5 http://ports.ubuntu.com/ubuntu-ports impish Release
#0 2.171 404 Not Found [IP: 185.125.190.39 80]
#0 2.322 Err:6 http://ports.ubuntu.com/ubuntu-ports impish-updates Release
#0 2.322 404 Not Found [IP: 185.125.190.39 80]
#0 2.475 Err:7 http://ports.ubuntu.com/ubuntu-ports impish-backports Release
#0 2.475 404 Not Found [IP: 185.125.190.39 80]
#0 2.623 Err:8 http://ports.ubuntu.com/ubuntu-ports impish-security Release
#0 2.623 404 Not Found [IP: 185.125.190.39 80]
#0 2.635 Reading package lists...
#0 2.652 E: The repository 'http://ports.ubuntu.com/ubuntu-ports impish Release' does not have a Release file.
#0 2.652 E: The repository 'http://ports.ubuntu.com/ubuntu-ports impish-updates Release' does not have a Release file.
#0 2.652 E: The repository 'http://ports.ubuntu.com/ubuntu-ports impish-backports Release' does not have a Release file.
#0 2.652 E: The repository 'http://ports.ubuntu.com/ubuntu-ports impish-security Release' does not have a Release file.
------
failed to solve: executor failed running [/bin/sh -c apt-get update && apt-get install -y gnupg gosu curl ca-certificates zip unzip git supervisor sqlite3 libcap2-bin libpng-dev python2 && mkdir -p ~/.gnupg && chmod 600 ~/.gnupg && echo "disable-ipv6" >> ~/.gnupg/dirmngr.conf && apt-key adv --homedir ~/.gnupg --keyserver hkps://keyserver.ubuntu.com --recv-keys 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C && echo "deb https://ppa.launchpadcontent.net/ondrej/php/ubuntu impish main" > /etc/apt/sources.list.d/ppa_ondrej_php.list && apt-get update && apt-get install -y php7.4-cli php7.4-dev php7.4-pgsql php7.4-sqlite3 php7.4-gd php7.4-curl php7.4-memcached php7.4-imap php7.4-mysql php7.4-mbstring php7.4-xml php7.4-zip php7.4-bcmath php7.4-soap php7.4-intl php7.4-readline php7.4-pcov php7.4-msgpack php7.4-igbinary php7.4-ldap php7.4-redis php7.4-xdebug && php -r "readfile('https://getcomposer.org/installer');" | php -- --install-dir=/usr/bin/ --filename=composer && curl -sL https://deb.nodesource.com/setup_$NODE_VERSION.x | bash - && apt-get install -y nodejs && npm install -g npm && curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - && echo "deb https://dl.yarnpkg.com/debian/ stable main" > /etc/apt/sources.list.d/yarn.list && apt-get update && apt-get install -y yarn && apt-get install -y mysql-client && apt-get install -y postgresql-client && apt-get -y autoremove && apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*]: exit code: 100
Script vendor/bin/sail up -d handling the start event returned with error code 17
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:
- Run
vendor/bin/sail up - Observe the error above
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (6 by maintainers)
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
@RuneSphinx
@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.
@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.