stackdriver-prometheus-sidecar: Can't use stackdriver container

Hi,

I have been trying to make this work for a while now and i’ve come to a few conclusions.

I can’t run any of the containers present in your public registry. Both locally and inside the clusters attempting to run your container results in this: standard_init_linux.go:190: exec user process caused "permission denied"

If I go and make the image myself, using make docker in the root directory, the generated container no longer has the error and I can start it up.

However, running your container from the gcloud console works and i’m able to get that one up straight away.

Docker info for local:

Containers: 56
 Running: 0
 Paused: 0
 Stopped: 56
Images: 1173
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:  (expected: 468a545b9edcd5932818eb9de8e72413e616e86e)
runc version: N/A (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: v0.18.0 (expected: fec3683b971d9c3ef73f284f176672c44b448662)
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-43-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.25GiB
Name: xxx
ID: HMKY:IVL6:OCB6:3OU5:PDDK:2XB7:2DJX:Q35N:D6DL:Z4ZB:JZBW:6DLF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

Docker info for gcp console:

Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 1
Server Version: 18.03.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.14.74+
Operating System: Debian GNU/Linux 9 (stretch) (containerized)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.656GiB
Name: cs-6000-devshell-vm-382718db-b6dd-4808-aaec-daaec04bd062
ID: 74SW:2GLN:6MQ2:IKIY:IGYQ:ZRRP:BSX3:JHHR:ALJO:LD3H:DLKH:SGI5
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 https://eu-mirror.gcr.io/
Live Restore Enabled: false

The ideal scenario would be being able to simply pull your container and run it. Have you seen this issue before?

Thanks.