Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[exotic platform, old kernel] docker driver fails #3780

Closed
minusdelta opened this issue Jan 22, 2018 · 4 comments
Closed

[exotic platform, old kernel] docker driver fails #3780

minusdelta opened this issue Jan 22, 2018 · 4 comments

Comments

@minusdelta
Copy link

I hesitated to post this, its possibly far out of your scope, but perhaps simple to fix ...

On this machine:
uname -r: 3.10.107-2-ARCH (not upgradable)
uname -m: armv7l
docker driver stopped working with nomad-0.6.0 (0.5.6 cannot be tested on arm, #2963).

Output on nomad-0.7.1:

[DEBUG] plugin: starting plugin: path=/usr/local/bin/nomad-0.7.1 args="[/usr/local/bin/nomad-0.7.1 executor {"LogFile":"/var/lib/nomad/alloc/32e8018e-edb2-fd76-b319-22fa3424fb83/test/executor.out","LogLevel":"INFO"}]"
[DEBUG] plugin: waiting for RPC address: path=/usr/local/bin/nomad-0.7.1
[DEBUG] plugin.nomad-0.7.1: plugin address: timestamp=2018-01-22T06:54:29.511Z address=/tmp/plugin768290409 network=unix
[INFO]  driver.docker: purged container e46627bb04786d6a9ec70e394e610079fccffac63956955b7983284c031ace35
[INFO]  driver.docker: created container da58fa76f47b3f18bd349f55797888ecc39a3982e8a79b9d8c4506e4269b9bd4
[ERR]   driver.docker: failed to start container da58fa76f47b3f18bd349f55797888ecc39a3982e8a79b9d8c4506e4269b9bd4: 
        API error (500): {"message":"OCI runtime create failed: container_linux.go:296: starting container process caused \"process_linux.go:398: 
        container init caused \\\"process_linux.go:365: setting cgroup config for procHooks process caused \\\\\\\"failed to write 0 to memory.swappiness: 
        write /sys/fs/cgroup/memory/docker/da58fa76f47b3f18bd349f55797888ecc39a3982e8a79b9d8c4506e4269b9bd4/memory.swappiness: invalid argument\\\\\\\"\\\"\": unknown"}
[DEBUG] plugin: plugin process exited: path=/usr/local/bin/nomad-0.7.1
[WARN]  client: failed to start task "test" for alloc "32e8018e-edb2-fd76-b319-22fa3424fb83": Failed to start container da58fa76f47b3f18bd349f55797888ecc39a3982e8a79b9d8c4506e4269b9bd4: API error (500): {"message":"OCI runtime create failed: container_linux.go:296: starting container process caused \"process_linux.go:398: container init caused \\\"process_linux.go:365: setting cgroup config for procHooks process caused \\\\\\\"failed to write 0 to memory.swappiness: write /sys/fs/cgroup/memory/docker/da58fa76f47b3f18bd349f55797888ecc39a3982e8a79b9d8c4506e4269b9bd4/memory.swappiness: invalid argument\\\\\\\"\\\"\": unknown"}
[INFO]  client: Restarting task "test" for alloc "32e8018e-edb2-fd76-b319-22fa3424fb83" in 15.370342586s
[INFO]  client.gc: marking allocation 32e8018e-edb2-fd76-b319-22fa3424fb83 for GC

Perhaps a fix a la: #3187 ?

cf. opencontainers/runc#20

@preetapan
Copy link
Contributor

preetapan commented Jan 22, 2018

@minusdelta thanks for reporting, we are going to add this to our list for the upcoming 0.8 release. Will be looking into whether we can set memory.swappiness to -1 in a backwards compatible way.

@preetapan preetapan self-assigned this Jan 22, 2018
@stale
Copy link

stale bot commented May 10, 2019

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

@stale
Copy link

stale bot commented Jun 9, 2019

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@stale stale bot closed this as completed Jun 9, 2019
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants