Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Problem on a Mac with elastic vm setting vm.max_map_count #68

Open
iKristjan opened this issue Jan 16, 2019 · 1 comment
Open

Problem on a Mac with elastic vm setting vm.max_map_count #68

iKristjan opened this issue Jan 16, 2019 · 1 comment

Comments

@iKristjan
Copy link
Contributor

This kills vagrant up for elastic vm on a Mac for me (MacOS 10.14, Docker Desktop Community Version 2.0.0.2):

inline: 'sudo sysctl -w vm.max_map_count=262144'

I get the following error:

==> elastic: Running trigger...
    elastic: Running local: Inline script
    elastic: sudo sysctl -w vm.max_map_count=262144
    elastic: sysctl: unknown oid 'vm.max_map_count'
==> elastic: Trigger run failed
==> elastic: A script exited with an unacceptable exit code 1.
A script exited with an unacceptable exit code 1.

It seems it's trying to set it for the Mac host (not Linux), which would not have the desired effect. An manual approach, which does seem to work for me is this: https://stackoverflow.com/a/51623813/2682119


Workaround I'm using for this is just overriding vagrant_triggers_mac_os in an local/service.elastic.yml file.

pm98zz-c pushed a commit that referenced this issue Feb 12, 2019
matason pushed a commit that referenced this issue Feb 12, 2019
* Fix plugin install (#67)

* Fix plugin install

* Switch version

* Use new version for base images

* Missing a WP test

* Fix Platform mismatch for SSH port forwarding

* Amend .gitignore for Ansible retry files

* #68: Remove sysctl call on Mac hosts
@pm98zz-c
Copy link
Contributor

The behaviour has been removed, question remains: do we want to try and properly do this, or just document it ?

@pm98zz-c pm98zz-c removed their assignment Feb 28, 2019
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