Yes, that appears to address both problems. Thanks!
* Pat Riehecky <[email protected]> [2019-06-10 14:18 -0500]: > I've dropped a possible fix package in the sl-testing repo. > > Can you try it to see if this resolves your issue? > > On 6/10/19 1:05 PM, Pat Riehecky wrote: > > I'll look into this. > > > > Pat > > > > On 6/10/19 9:59 AM, Phil Gold wrote: > > > I've been having two problems with the newest docker packages in the > > > sl-extras repository for Scientific Linux 7. I'm not sure where to > > > report > > > them so hopefully someone here will help. > > > > > > > > > The first problem appears to be one of packaging. The systemd unit file > > > for docker-1.13.1-96.gitb2f74b2.sl7.x86_64 contains references to > > > `rhel-push-plugin.socket`, which is not present in any Scientific Linux > > > packages, as far as I can tell. I have to remove all references to that > > > unit file in order to start docker. The previous RPM > > > (1.13.1-94.gitb2f74b2.sl7) did not have this problem. > > > > > > > > > The second problem is that I cannot `docker exec` things in some > > > (but not > > > all) of my containers. For the ones that fail, I get the following > > > error > > > message: > > > > > > rpc error: code = 2 desc = oci runtime error: exec failed: > > > container_linux.go:235: starting container process caused > > > "process_linux.go:110: decoding init error from pipe caused \"read > > > parent: connection reset by peer\"" > > > > > > This looks to me a lot like bug #1655214 in the Red Hat Bugzilla: > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1655214&d=DwIBAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=cUDmEKgsvyvfXqxPWpSYuUAAT0eU2MkIq2JcEGVEAUY&s=td7JS4nXUFG8wQzmEEoEIlnKTwj8InHnoIurYBnXeX4&e= > > > > > > Unfortunately, that bug was closed with Red Hat's > > > 1.13.1-88git07f3374.el7 > > > docker RPM, whereas I'm seeing problems with Scientific Linux's > > > 1.13.1-96.gitb2f74b2.sl7 and 1.13.1-94.gitb2f74b2.sl7 docker RPMs. > > > > > > Is it possible I'm doing something wrong, or is this a bug that > > > should be > > > reported? If it's a bug, where should I report it (and my other > > > problem)? > > > I haven't found anything for Scientific Linux like Red Hat's Bugzilla > > > instance. > > > > > > Just in case it's relevant, I have four different images I've tested > > > things with. All of them are from the Docker Hub registry. > > > > > > * mariadb:10 has problems. It's ultimately based on ubuntu:bionic. > > > > > > * mediawiki:1.31 has problems. It's ultimately based on > > > debian:stretch-slim. > > > > > > * centos/httpd-24-centos7 does not have problems. It's ultimately > > > based > > > on centos:7. > > > > > > * dperson/samba:latest has problems. It's ultimately based on > > > alpine:latest. > > > > > > `docker exec` works properly on all of them when I'm using the > > > docker-1.13.1-91.git07f3374.sl7 RPM from the sl-extras repository. The > > > problems consistently appear, both in my images and in the base images, > > > with any later RPMs. > > > > > > -- Phil Gold JHU CS IT Support (Linux)
