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

How to change kernel for "docker-machine" #2895

Closed
peterromfeldhk opened this issue May 10, 2018 · 7 comments
Closed

How to change kernel for "docker-machine" #2895

peterromfeldhk opened this issue May 10, 2018 · 7 comments

Comments

@peterromfeldhk
Copy link

peterromfeldhk commented May 10, 2018

or whats the best way to run docker on OSX but be able to change kernel of the actual VM running docker?

@stephen-turner
Copy link
Contributor

Why do you want to do this?

@YRM64
Copy link

YRM64 commented May 11, 2018

You have to change the kernel configurations, however, I too would like to know why you need to change the kernel for Docker-for-Mac?

@peterromfeldhk
Copy link
Author

we encountered a issue and suspected its related to a bug in this old kernel that is used.

we ended up running docker(CI runner) on a spare Linux machine instead which allowed a complete different approach to the issue.

@stephen-turner
Copy link
Contributor

OK, glad you got it working. I’m going to close this issue now, although I’m not aware of any bugs related to the version of the kernel used: it should be an internal implementation detail as far as the user is concerned.

@mageekguy
Copy link

Hi!

Firstly, thanks for your good job.
Secondly, upgrading kernel version may be a very good idea, because currently, it's not possible to use net.ipv4.ip_unprivileged_port_start=0 as a sysctl entry because this instruction is available only since kernel version ≥ 4.11.
And this instruction is very useful to bind (for example) apache on a privileged port (aka 80) as a non-root user (see moby/moby#8460).

@morganchristiansson
Copy link

morganchristiansson commented Jan 28, 2019

I'm getting this error trying to run container as non-root user:

ERROR: for myproject_myservice_1  Cannot start service myservice: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"open /proc/sys/net/ipv4/ip_unprivileged_port_start: no such file or directory\"": unknown

As you say this is because of old Linux kernel in Docker for Mac.... CAP_NET_BIND doesn't work correctly either so will have to find a different approach to allow privileged port.... Following advice in moby/moby#8460 (comment)

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 28, 2020
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

6 participants