exec user process caused "no such file or directory" for docker run glowroot/glowroot-central:0.13.6

1,174 views
Skip to first unread message

Erik Ostermueller

unread,
Mar 24, 2020, 11:15:42 AM3/24/20
to Glowroot
Hi all,

I've got glowroot's cassandra image up and going, but I could use some help launching the glowroot central image.

Here's my environment:

# glowrootCentral]$ docker --version
Docker version 19.03.8, build afacb8b
# glowrootCentral]$ uname -a
Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Mon Dec 2 08:31:54 EST 2019 x86_64 x86_64 x86_64 GNU/Linux

When I run "sudo docker start $GLOWROOT_CONTAINER_ID " the container doesn't start.  my ps -a shows "Exited (1) 14 minutes ago"

So I'm trying to open a bash shell to troubleshoot inside the image.
When I try this command:
sudo docker run -i -t glowroot/glowroot-central:0.13.6 /bin/bash

I get the following error:

standard_init_linux.go:211: exec user process caused "no such file or directory"

The links below suggests that linux is choking on MS-Win crlf issues....but I'm not really sure.
Any suggestions on how to get this image to start on linux?

We love glowroot, thanks for sharing,

--Erik


Erik Ostermueller

unread,
Mar 24, 2020, 11:39:26 AM3/24/20
to Glowroot
Here is an easier way to reproduce:

[# glowrootCentral]$ docker run --name myglowroot --link mycassandra:cassandra -p 127.0.0.1:4000:4000 glowroot/glowroot-central:0.13.6
standard_init_linux.go:211: exec user process caused "no such file or directory"

Erik Ostermueller

unread,
Mar 26, 2020, 9:55:00 AM3/26/20
to Glowroot
Whoops, known issue:
https://github.com/glowroot/glowroot/issues/626

I'll work on building the image myself and retrying.
Reply all
Reply to author
Forward
0 new messages