moby: Setting OOM score for ready process caused "write /proc/5578/oom_score_adj: invalid argument"
Output of docker version
:
Client:
Version: 1.12.0-rc4
API version: 1.24
Go version: go1.6.2
Git commit: e4a0dbc
Built: Wed Jul 13 03:28:51 2016
OS/Arch: darwin/amd64
Experimental: true
Server:
Version: 1.12.0-rc4
API version: 1.24
Go version: go1.6.2
Git commit: e4a0dbc
Built: Wed Jul 13 03:28:51 2016
OS/Arch: linux/amd64
Experimental: true
Output of docker info
:
Containers: 16
Running: 7
Paused: 0
Stopped: 9
Images: 72
Server Version: 1.12.0-rc4
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 332
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.954 GiB
Name: moby
ID: Z3AR:3OHB:47FY:H22B:IWGM:IFLR:T7SP:IRUW:SOSA:43U6:D77Z:B2HP
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 55
Goroutines: 82
System Time: 2016-07-27T00:02:38.724549572Z
EventsListeners: 1
No Proxy: *.local, 169.254/16
Username: alfonsoperez
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
127.0.0.0/8
Additional environment details (AWS, VirtualBox, physical, etc.):
docker for mac
Steps to reproduce the issue:
docker-compose ..../docker-compose.yml up web
Describe the results you received:
ERROR: for web oci runtime error: process_linux.go:295: setting oom score for ready process caused "write /proc/5578/oom_score_adj: invalid argument"
Describe the results you expected:
Starting the container
Additional information you deem important (e.g. issue happens only occasionally):
Tried restarting docker / removing the containers several times
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 24 (19 by maintainers)
Ran into this issue with Kubernetes setting an env var from a secret. The fix was to base64 encode the secret value. I believe kubernetes automatically decodes secrets when it mounts them onto a pod.
Ok, from the other issue here is a minimal Dockerfile that replicates this
There should not of course be a
$
in theENV
line, and this seems to cause the issue, for non obvious reasons.@alfonsoperez do you have any extra
$
in yourenv-file
?