Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 18 22:24
    stale[bot] labeled #2820
  • Apr 18 22:24
    stale[bot] commented #2820
  • Apr 17 13:52

    Mahmoudz on gh-pages

    Deploy laradock/laradock to git… (compare)

  • Apr 17 13:11

    bestlong on master

    fix incomplete SSL chain error … Merge pull request #2805 from a… (compare)

  • Apr 17 13:11
    bestlong closed #2805
  • Apr 17 13:09

    bestlong on v12.1

    (compare)

  • Apr 17 10:18

    bestlong on all-in

    (compare)

  • Apr 17 10:18

    bestlong on fix-2943

    (compare)

  • Apr 17 10:18

    bestlong on ci-schedule-not-trigger-in-fork

    (compare)

  • Apr 17 10:18

    bestlong on enchant

    (compare)

  • Apr 17 10:04

    Mahmoudz on gh-pages

    Deploy laradock/laradock to git… (compare)

  • Apr 17 09:53

    bestlong on master

    php-fpm support enchant extensi… Merge pull request #2953 from l… (compare)

  • Apr 17 09:53
    bestlong closed #2953
  • Apr 17 08:24
    bestlong edited #2953
  • Apr 17 08:22
    bestlong opened #2953
  • Apr 17 08:20

    bestlong on enchant

    php-fpm support enchant extensi… (compare)

  • Apr 17 08:20

    Mahmoudz on gh-pages

    Deploy laradock/laradock to git… (compare)

  • Apr 17 08:18

    bestlong on master

    fix horizon memcached php-worker support memcached ex… Merge pull request #2952 from l… (compare)

  • Apr 17 08:18
    bestlong closed #2952
  • Apr 17 08:18
    bestlong closed #2828
sung1asses
@sung1asses
image.png
Alex Millman
@millman2394

Hi guys, I'm trying to run Puppeteer. I get an error saying error while loading shared libraries: libnss3.so

There is troubleshooter for docker: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-puppeteer-in-docker

But i'm not sure where to put that

tariqbilal
@tariqbilal

Let's say I have an EC2 Server which needs to have multiple developers working on. I want to configure same project on multiple ports. So that each developer working remotely

should have

1- it's seperate User

2- Seperate project directory

3- Run on Laradock different port (for example User 1 could use port 80, User 2 could use port 5000).

4- The User will have seperate host names so that they can be reached on the browser.

I can configure for first user with port 80 but the other developers sites are unable to serve with port 5000 etc.

Has anyone configured a multi site with hosts on laradock ?

Richathon
@Richathon
Hi everyone, i would like to enable horizon in laradock by command php artisan horizon. But i got this error message. "Please make sure the PHP Redis extension is installed and enabled"
  • This is image of errors refer: https://i.stack.imgur.com/YXIm4.png
  • In .env file of laravel project i have editted:
    REDIS_HOST=redis
    REDIS_PASSWORD=null
    REDIS_PORT=6379
  • I have enabled all INSTALL_PHPREDIS=true in .env of laradock folder. After that run "docker-compose build --no-cache workspace php-fpm php-worker". This is the .env file of laradock
    => After many trying i still that errors, it's my mistake of any configuration or Laradock changes something
    Please help me this case, i've spent 2 days just for this :(
mli-Scofield
@mli-Scofield
ERROR: Installation aborted, plugin 'logstash-input-jdbc' is already provided by 'logstash-integration-jdbc'
harrisdt15f
@harrisdt15f
image.png
10 replies
Hello I got this error on building workspace
please someone help me.
harrisdt15f
@harrisdt15f
image.png
harrisdt15f
@harrisdt15f
image.png
harrisdt15f
@harrisdt15f
after I upgraded the docker desktop v 3.2.2 and then got the error I don't know if it is cause by upgrade of docker desktop. someone light me.
victor amestica
@amestica.victor_gitlab
hola
alguien tiene problemas con el contenedor workspace
en la parte de msssql?
con PHP 7.2?
Mick Byrne
@ArtisanTinkerer
Are there any plans to update Laradock for PHP 8 (and Xdebug 3)?
Shao Yu-Lung (Allen)
@bestlong
@harrisdt15f workspace max depth exceeded problem fixed by laradock/laradock#2910
Georges Salloum
@gsalloum_gitlab
Hello, anyone worked with informix db drivers on laravel docker swarm?
im facing issues getting a service up with proper drivers, last successfull run was on docker with no swarm, i had a centos 7 dockerfile with systemd commands to configure informix....apparently swarm does not allow "--privileged" argument (needed form systemd commands) are not compatible and the containers aren't starting
Georges Salloum
@gsalloum_gitlab
image.png
I'm getting this error....sorry if this the wrong thread, just trying to figure out the proper way to run php informix with laravel
Mick Byrne
@ArtisanTinkerer
Has anyone got ClamAV working? I have the service running on my php-fpm container but get: ClamAV scanner client failed with error "Socket operation failed: Connection refused (SOCKET_ECONNREFUSED)"
Scott Spittle
@ScottSpittle

Hi, I can't seem to get XDebug working after updating to PHP 8 and XDebug 3.

It's installed and running as I can see from php -v.

My php-fpm xdebug.ini is

xdebug.remote_connect_back=0
xdebug.remote_port=9000
xdebug.idekey=PHPSTORM

xdebug.remote_autostart=0
xdebug.remote_enable=0
xdebug.cli_color=0
xdebug.profiler_enable=0
xdebug.profiler_output_dir="~/xdebug/phpstorm/tmp/profiling"

xdebug.remote_handler=dbgp
xdebug.remote_mode=req

xdebug.var_display_max_children=-1
xdebug.var_display_max_data=-1
xdebug.var_display_max_depth=-1

I am using InteliJ IDEA to interact with XDebug in Laradock

harrisdt15f
@harrisdt15f
xdebug.client_port=9003
xdebug 3 use 9003
Scott Spittle
@ScottSpittle
OK @harrisdt15f I'll give that a go, thanks for the quick reply
harrisdt15f
@harrisdt15f
i think your config like old xdebug config
in xdebug3 it should be xdebug.client_port=9003 and xdebug.client_host="host.docker.internal"
14 replies
harrisdt15f
@harrisdt15f
image.png
Scott Spittle
@ScottSpittle
image.png
Scott Spittle
@ScottSpittle

I get the following xdebug log output when trying to use xdebug

[6] Log opened at 2021-03-31 14:27:55.089223
[6] [Step Debug] INFO: Checking remote connect back address.
[6] [Step Debug] INFO: Checking header 'HTTP_X_FORWARDED_FOR'.
[6] [Step Debug] INFO: Checking header 'REMOTE_ADDR'.
[6] [Step Debug] INFO: Client host discovered through HTTP header, connecting to 172.30.0.1:9003.
[6] [Step Debug] INFO: Connected to debugging client: 172.30.0.1:9003 (from REMOTE_ADDR HTTP header). :-)
[6] [Step Debug] -> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/public/index.php" language="PHP" xdebug:language_version="8.0.3" protocol_version="1.0" appid="6" idekey="PHPSTORM"><engine version="3.0.0"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[https://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2020 by Derick Rethans]]></copyright></init>

[6] [Step Debug] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response>

[6] [Step Debug] WARN: 2021-03-31 14:27:55.709090: There was a problem sending 179 bytes on socket 7: Broken pipe.
[6] Log closed at 2021-03-31 14:27:55.710934

I'm not sure how to resolve it

Scott Spittle
@ScottSpittle
I've resolved the issue, port 9003 was in use
cyyyrcyx
@cyyyrcyx
Why doesn't laradock support php8?
cyyyrcyx
@cyyyrcyx
npm notice
npm notice New minor version of npm available! 7.7.6 -> 7.8.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.8.0
npm notice Run npm install -g npm@7.8.0 to update!
npm notice
v15.13.0 is already installed.
Now using node v15.13.0 (npm v7.7.6)
Now using node v15.13.0 (npm v7.7.6)
node -> stable (-> v15.13.0) (default)
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! code EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! errno EAI_AGAIN
harrisdt15f
@harrisdt15f
image.png
hello somone tell me please i cann't see message detail of queue
I have already added permission to guest user it still cann't show the message pannel of queue on the right sight.
Gilbok Lee
@gilbok

Hi, anyone experienced mmap() failed: [12] Cannot allocate memory
when you php artisan tinker or composer install in workspace's bash shell
on Apple M1 MacBook?

The difference between M1 MacBook and Intel MacBook is free memory.

The initial free memory of workspace on M1 MacBook is just 108MB.

root@3eea29411f48 /var/www/ $ free -m
              total        used        free      shared  buff/cache   available
Mem:           1988         700         108         345        1180         845
Swap:          1023          89         934

But the initial free memory on Intel Macbook is 306MB.

root@2deae966d1f9:/var/www/ $ free -m
              total        used        free      shared  buff/cache   available
Mem:           1988         528         306          18        1153        1288
Swap:          1023         560         46
Gilbok Lee
@gilbok
UPDATE: I tried it again after I had VM have more free memory. But it still occurs mmap() failed: [12] Cannot allocate memory error. Maybe it is not related to this error.
root@b179f678a927 /var/www/testapp $ free -m
              total        used        free      shared  buff/cache   available
Mem:           2657         753         646         395        1256        1370
Swap:          1023           0        1023
root@b179f678a927 /var/www/testapp $ php artisan tinker
mmap() failed: [12] Cannot allocate memory

mmap() failed: [12] Cannot allocate memory
PHP Fatal error:  Out of memory (allocated 10485760) (tried to allocate 4096 bytes) in /var/www/testapp/vendor/composer/autoload_static.php on line 4660
Gilbok Lee
@gilbok
Now I think it is not a memory issue, it's an architecture issue.
I got a hint from Laraberries(laradock forked). I will try the workspace container built for ARM64.
cyyyrcyx
@cyyyrcyx
Did you give up laradock?
Why is there no popularity?
Is laradock not ready to support php8?
cyyyrcyx
@cyyyrcyx
0curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused
/bin/sh: 1: .: Can't open /home/laradock/.nvm/nvm.sh
Can this problem be fixed?
cyyyrcyx
@cyyyrcyx
---> Running in ec34296bd549
  • apt-get update -yqq
    E: The repository 'http://security.ubuntu.com/ubuntu bionic-security Release' no longer has a Release file.
    E: The repository 'http://ppa.launchpad.net/ondrej/php/ubuntu bionic Release' no longer has a Release file.
    E: The repository 'http://archive.ubuntu.com/ubuntu bionic Release' no longer has a Release file.
    E: The repository 'http://archive.ubuntu.com/ubuntu bionic-updates Release' no longer has a Release file.
    E: The repository 'http://archive.ubuntu.com/ubuntu bionic-backports Release' no longer has a Release file.
    The command '/bin/sh -c set -xe; apt-get update -yqq && pecl channel-update pecl.php.net && groupadd -g ${PGID} laradock && useradd -l -u ${PUID} -g laradock -m laradock -G docker_env && usermod -p "*" laradock -s /bin/bash && apt-get install -yqq apt-utils libzip-dev zip unzip php${LARADOCK_PHP_VERSION}-zip nasm && php -m | grep -q 'zip'' returned a non-zero code: 100
    ERROR: Service 'workspace' failed to build
DanielF
@DanielFloris

I'm getting a lot of these in my log files

 php_network_getaddresses: getaddrinfo failed: Name or service not known [tcp://redis:6379] {"exception":"[object]

Redis seems to be working ok, as does everything else. Any idea what could be causing it?

cyyyrcyx
@cyyyrcyx
Will laradock stop updating?
Shao Yu-Lung (Allen)
@bestlong

I'm getting a lot of these in my log files

 php_network_getaddresses: getaddrinfo failed: Name or service not known [tcp://redis:6379] {"exception":"[object]

Redis seems to be working ok, as does everything else. Any idea what could be causing it?

check docker-compose ps

Alexandre Lima
@LexSombra
Hey everyone!
Has anyone been able to configure browser debugging on PHP storm with the recent laradock versions?
When I try do listen for connections on PHP storm I get that port 9003 is already in use, but I'm using the exact same configuration as before, so I guess something changed on laradock's side.
Only PHPStorm and Laradock are using the port, so PHP fails to listen when Laradock is running and also laradock fails to start when phpstorm is running...
Something is off
Alexandre Lima
@LexSombra

I was able to fix it:
1 - Remove those lines from DockerCompose.yml in the PHP-FPM section:
ports:

    - "${PHP_FPM_XDEBUG_PORT}:9003"

2 - On php-fpm/xdebug.ini:

xdebug.remote_host="host.docker.internal" => ;xdebug.remote_host="host.docker.internal"
xdebug.remote_connect_back=0 => xdebug.remote_connect_back=1

Now everything works fine again. (I suck at Gitter's code formmating, bug I guess you can understand)