Workspace crash after few seconds

[pio2398]

Info:

• Docker version ($ docker --version): Docker version 18.09.0-ce, build 4d60db472b
• Laradock commit ($ git rev-parse HEAD): d8c36ab
• System info (Mac, PC, Linux): Linux
• System info disto/version: Arch

Issue:

Workspace crash after few seconds

sudo docker-compose up workspace
laradock_docker-in-docker_1 is up-to-date
Starting laradock_workspace_1 ... done
Attaching to laradock_workspace_1
workspace_1            | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
workspace_1            | *** Running /etc/my_init.d/10_syslog-ng.init...
workspace_1            | Dec 22 18:33:07 8eb813758067 syslog-ng[10]: syslog-ng starting up; version='3.5.6'
workspace_1            | Dec 22 18:33:07 8eb813758067 syslog-ng[10]: Error opening control socket, bind() failed; socket='/var/lib/syslog-ng/syslog-ng.ctl', error='Permission denied (13)'
workspace_1            | Dec 22 18:33:07 8eb813758067 syslog-ng[10]: WARNING: you are using the pipe driver, underlying file is not a FIFO, it should be used by file(); filename='/dev/stdout'
workspace_1            | *** /etc/my_init.d/10_syslog-ng.init failed with status 1
workspace_1            | 
workspace_1            | *** Killing all processes...
workspace_1            | Dec 22 18:33:37 8eb813758067 syslog-ng[10]: syslog-ng shutting down; version='3.5.6'

---

Expected behavior:

Should work

---

Reproduce:

Just start workshop

---

Relevant Code:

// place a code sample here

[bestlong]

run on mac

~/Sites/laradock (master *)$ docker-compose up -d workspace
Creating network "laradock_frontend" with driver "bridge"
Creating network "laradock_backend" with driver "bridge"
Creating network "laradock_default" with the default driver
Creating laradock_docker-in-docker_1 ... done
Creating laradock_workspace_1        ... done
~/Sites/laradock (master *)$ docker-compose logs workspace
Attaching to laradock_workspace_1
workspace_1            | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
workspace_1            | *** Running /etc/my_init.d/10_syslog-ng.init...
workspace_1            | Feb 11 14:02:32 e817a869bb9d syslog-ng[11]: syslog-ng starting up; version='3.5.6'
workspace_1            | Feb 11 14:02:32 e817a869bb9d syslog-ng[11]: WARNING: you are using the pipe driver, underlying file is not a FIFO, it should be used by file(); filename='/dev/stdout'
workspace_1            | Feb 11 14:02:33 e817a869bb9d syslog-ng[11]: EOF on control channel, closing connection;
workspace_1            | *** Running /etc/rc.local...
workspace_1            | *** Booting runit daemon...
workspace_1            | *** Runit started as PID 17
workspace_1            | Feb 11 14:02:33 e817a869bb9d cron[20]: (CRON) INFO (pidfile fd = 3)
workspace_1            | Feb 11 14:02:33 e817a869bb9d cron[20]: (CRON) INFO (Running @reboot jobs)
~/Sites/laradock (master *)$ git log --pretty=oneline -1
d27f4368eec570d0a6a12136cb8476fbc1cb343a (HEAD -> master) Run bash when login by `laradock` via ssh (#1541)
~/Sites/laradock (master *)$

[jeff-h]

@bestlong what does docker-compose logs workspace do in this context? When I run it, it just seems to display a copy of all the log history from the container. However it does also appear to have stopped that warning entry appearing in the log over and over, but I'd really like to understand why.

[bestlong]

@jeff-h docker-compose logs workspace just show workspace container all log. for compare what are the differnces.

[lbssousa]

I'm facing the same problem here. I'm currently running Docker CE v19.03.1with Docker Compose v1.24.1 on Arch Linux.

This is the output of my docker-compose logs workspace:

workspace_1            | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
workspace_1            | *** Running /etc/my_init.d/10_syslog-ng.init...
workspace_1            | Error parsing source, source plugin unix-dgram not found in /etc/syslog-ng/syslog-ng.conf at line 21, column 8:
workspace_1            | 
workspace_1            |        unix-dgram("/dev/log");
workspace_1            |        ^^^^^^^^^^
workspace_1            | 
workspace_1            | syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
workspace_1            | mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng
workspace_1            | *** /etc/my_init.d/10_syslog-ng.init failed with status 1
workspace_1            | 
workspace_1            | *** Killing all processes...

[lbssousa]

It seems this bug is related to upstream phusion/baseimage project.

Related issue: phusion/baseimage-docker#540

[dziurka]

I have the same problem. Unfortunately

[ohahlev]

I am having the exact same problem. I am on Solus.

At the beginning, they're all up.

ahlev@home ~/Projects/ahlev-laravel-dyndb/laradock $ docker-compose ps
           Name                          Command               State                    Ports                  
---------------------------------------------------------------------------------------------------------------
laradock_docker-in-docker_1   dockerd-entrypoint.sh            Up      2375/tcp, 2376/tcp                      
laradock_mysql_1              docker-entrypoint.sh mysqld      Up      0.0.0.0:3306->3306/tcp, 33060/tcp       
laradock_nginx_1              /bin/bash /opt/startup.sh        Up      0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
laradock_php-fpm_1            docker-php-entrypoint php-fpm    Up      9000/tcp                                
laradock_phpmyadmin_1         /docker-entrypoint.sh apac ...   Up      0.0.0.0:8080->80/tcp                    
laradock_redis_1              docker-entrypoint.sh redis ...   Up      0.0.0.0:6379->6379/tcp                  
laradock_workspace_1          /sbin/my_init                    Up      0.0.0.0:2222->22/tcp

After a few seconds

ahlev@home ~/Projects/ahlev-laravel-dyndb/laradock $ docker-compose ps
           Name                          Command               State                     Ports                  
----------------------------------------------------------------------------------------------------------------
laradock_docker-in-docker_1   dockerd-entrypoint.sh            Up       2375/tcp, 2376/tcp                      
laradock_mysql_1              docker-entrypoint.sh mysqld      Up       0.0.0.0:3306->3306/tcp, 33060/tcp       
laradock_nginx_1              /bin/bash /opt/startup.sh        Up       0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
laradock_php-fpm_1            docker-php-entrypoint php-fpm    Up       9000/tcp                                
laradock_phpmyadmin_1         /docker-entrypoint.sh apac ...   Up       0.0.0.0:8080->80/tcp                    
laradock_redis_1              docker-entrypoint.sh redis ...   Up       0.0.0.0:6379->6379/tcp                  
laradock_workspace_1          /sbin/my_init                    Exit 1 

and here is the log of workspace

ahlev@home ~/Projects/ahlev-laravel-dyndb/laradock $ docker-compose logs workspace 
Attaching to laradock_workspace_1
workspace_1            | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
workspace_1            | *** Running /etc/my_init.d/10_syslog-ng.init...
workspace_1            | Error parsing source, source plugin unix-dgram not found in /etc/syslog-ng/syslog-ng.conf at line 21, column 8:
workspace_1            | 
workspace_1            |        unix-dgram("/dev/log");
workspace_1            |        ^^^^^^^^^^
workspace_1            | 
workspace_1            | syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
workspace_1            | mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng
workspace_1            | *** /etc/my_init.d/10_syslog-ng.init failed with status 1

My purpose is to create laravel project after gaining access to the workspace using composer...blah..blah; I don't want to install composer in my system; I want it, and everything else inside the container.

[stale]

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.