Skip to content

doc: add exact informations to disable apparmor #3515

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.

Sign up for GitHub

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

Merged
sougou merged 1 commit into from
Dec 29, 2017
Merged

doc: add exact informations to disable apparmor #3515

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion doc/GettingStarted.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,16 @@ In addition, Vitess requires the software and libraries listed below.
various permission failures when Vitess initializes MySQL instances through
the `mysqlctl` tool. This is only an issue for a test environment. If AppArmor
is necessary in production, you can configure the MySQL instances appropriately
without going through mysqlctl. (TODO(sougou): provide exact instructions).
without going through mysqlctl.

``` sh
$ sudo service apparmor stop
$ sudo service apparmor teardown
$ sudo update-rc.d -f apparmor remove
```

Reboot, just to be sure that `AppArmor` is fully disabled.


4. Select a lock service from the options listed below. It is technically
possible to use another lock server, but plugins currently exist only
Expand Down
9 changes: 8 additions & 1 deletion docs/getting-started/local-instance/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -426,7 +426,14 @@ <h4 id="ubuntu-and-debian">Ubuntu and Debian</h4>
various permission failures when Vitess initializes MySQL instances through
the <code class="prettyprint">mysqlctl</code> tool. This is only an issue for a test environment. If AppArmor
is necessary in production, you can configure the MySQL instances appropriately
without going through mysqlctl. (TODO(sougou): provide exact instructions).</p></li>
without going through mysqlctl.
<div class="highlight"><pre><code class="language-sh" data-lang="sh">
<span></span>$ sudo service apparmor stop
<span></span>$ sudo service apparmor teardown
<span></span>$ sudo update-rc.d -f apparmor remove
</code></pre></div>
Reboot, just to be sure that <code class="prettyprint">AppArmor</code> is fully disabled.
</p></li>
<li><p>Select a lock service from the options listed below. It is technically
possible to use another lock server, but plugins currently exist only
for ZooKeeper, etcd and consul.</p>
Expand Down