Odd Bundle Inconsistencies about ansible-silo HOT 7 CLOSED

Good morning Brady,

that's very strange. But I don't think the problem lies in the image/container, there really is not much that could go wrong.

I see the 1st install command of the bundle was executed as user bl839s and the 2nd install command of ansible-silo was executed as root. I'm guessing there is a difference in the env and user bl839s doesn't have bash in the PATH.

Can bl839s call bash? What do those command show?

/usr/bin/env bash --version

command -v bash

The latter command should show the location of bash. Is the parent directory in $PATH?

Compare:

echo $PATH
sudo echo $PATH

Unfortunately this is the only pointer I can give for now. Again, really strange.

Thanks again for all of the help given so far and I apologize for continuing to come back with problems, but hopefully it will just help ansible-silo become better in the process.

Exactly! So don't worry, you're always welcome and I'm happy silo is being used out there.

Cheers,
Daniel

from ansible-silo.

Yeah, I tried installing the bundle both my user and as root with the same results.

I thought the same as well from your comment:

But I don't think the problem lies in the image/container, there really is not much that could go wrong.

Here is the output of the requested commands:

[bl839s@bld-apic-em-1 ~]$ /usr/bin/env bash --version
GNU bash, version 4.2.46(2)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[bl839s@bld-apic-em-1 ~]$ command -v bash
/usr/bin/bash

[bl839s@bld-apic-em-1 ~]$ echo $PATH
/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin

[bl839s@bld-apic-em-1 ~]$ su
Password:
[root@bld-apic-em-1 bl839s]# echo $PATH
/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin

I'm not an expert in Linux, but from what I can tell, it should work fine, something is apparently off though.
I'll keep working on it as much as I can and let you know when and if I come up with anything.

Thanks.

from ansible-silo.

Still trying to troubleshoot this same issue...
I know you're not able to troubleshoot docker problems, but I thought I would ask just in case.

After trying all sorts of things, I just tried installing ansible-silo again per the instructions on your GitHub page and I encountered this error:

[root@bld-apic-em-1 bl839s]# docker run --interactive --tty --rm --volume "/usr/local/bin:/silo_install_path" grpn/ansible-silo:2.1.0 --install
standard_init_linux.go:185: exec user process caused "no such file or directory"

My GoogleFu has been pointing to incorrect line endings (windows causes issues), but I haven't touched anything on this system with Windows.

I'm using a fairly recent version of docker:

[root@bld-apic-em-1 bl839s]# docker --version
Docker version 17.09.1-ce, build 19e2cf6

Which at a basic level seems to work fine:

[root@bld-apic-em-1 bl839s]# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
ca4f61b1923c: Pull complete
Digest: sha256:083de497cff944f969d8499ab94f07134c50bcf5e6b9559b27182d3fa80ce3f7
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://cloud.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/engine/userguide/

But when I try and run this container, I get the same error:

[root@bld-apic-em-1 bl839s]# docker run grpn/ansible-silo:2.1.0
standard_init_linux.go:185: exec user process caused "no such file or directory"

I'm grasping at straws trying to understand why this production system is behaving drastically different than all of my development systems.

from ansible-silo.

Leaving a breadcrumb: here's the code for the version of docker-ce that you're using:

• https://github.com/docker/docker-ce/tree/v17.09.1-ce

from ansible-silo.

If I'm correct in my guess about how docker builds up its distribution, here's the place they set the runc version:

• https://github.com/docker/docker-ce/blob/v17.09.1-ce/components/engine/hack/dockerfile/binaries-commits#L6

RUNC_COMMIT=3f2f8b84a77f73d38244dd690525642a72156c64

Which leads to the runc code here:

• https://github.com/opencontainers/runc/blob/3f2f8b84a77f73d38244dd690525642a72156c64/libcontainer/standard_init_linux.go#L185

P.S., I had previously figured out that this file was in runc by using github to search for the filename in the docker org:

• https://github.com/search?q=org%3Adocker+filename%3Astandard_init_linux.go&type=Code&utf8=%E2%9C%93

That led to this repo:

• https://github.com/docker/libcontainer

Which indicates it was moved to here:

• https://github.com/opencontainers/runc

from ansible-silo.

I wonder why they don't include the failing command in the error... you can possibly hand-hack the library to that.

from ansible-silo.

Similar to issue #54:

I've been able to solve this by rebuilding grpn/ansible-silo-base:3.0.0 and grpn/ansible-silo:3.0.0.
I'm still working through some issues, but when I'm ready, I will submit a PR.

from ansible-silo.