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.

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

Jump to bottom

Update README to reference enable-admin-container #413

Merged
merged 1 commit into from
Oct 15, 2019
Merged

Update README to reference enable-admin-container #413

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
10 changes: 7 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,15 +111,19 @@ To enable the container, you can change the setting in user data when starting T
settings.host-containers.admin.enabled = true
```

If Thar is already running, you can change the setting with an API call:
If Thar is already running, you can enable the admin container from the default [control container](#control-container) like this:

```
enable-admin-container
```

If you're using a custom control container, or want to make the API calls directly, you can enable the admin container like this instead:

```
apiclient -u /settings -m PATCH -d '{"host-containers": {"admin": {"enabled": true}}}'
apiclient -u /settings/commit_and_apply -m POST
```

(To make an API call like this, you need to use an authenticated channel like [SSM](#control-container).)

Once you're in the admin container, you can run `sheltie` to get a full root shell in the Thar host.
Be careful; while you can inspect and change even more as root, Thar's filesystem and dm-verity setup will prevent most changes from persisting over a restart - see [Security](#security).

Expand Down