-
Notifications
You must be signed in to change notification settings - Fork 416
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(docs): update aarch64 references to latest in docs
commit: d2b8dbe (main), cherry-pick
- Loading branch information
1 parent
59ee33d
commit a775700
Showing
3 changed files
with
17 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,13 +4,14 @@ This section details how you can run Tracee through a container image. | |
|
||
## Prerequisites | ||
|
||
Please ensure that Docker or another container runtime is working on your machine. | ||
Please ensure that Docker or another container runtime is working on your machine. | ||
|
||
## Run the Tracee container images | ||
|
||
All of the Tracee container images are stored in a public registry on [Docker Hub.](https://hub.docker.com/r/aquasec/tracee) | ||
You can easily start experimenting with Tracee using the Docker image. | ||
|
||
### On x86 architecture, please run the following command: | ||
### On x86 architecture, please run the following command | ||
|
||
```console | ||
docker run \ | ||
|
@@ -20,45 +21,45 @@ docker run \ | |
aquasec/tracee:latest | ||
``` | ||
|
||
### Steps to run the Tracee container image on arm64: | ||
### Steps to run the Tracee container image on arm64 | ||
|
||
There are a few more steps involved in running Tracee through a container image on arm64 (M1). | ||
|
||
Prerequisites: | ||
|
||
* [Vagrant CLI](https://developer.hashicorp.com/vagrant/downloads) installed | ||
* [Parallels Pro](https://www.parallels.com/uk/products/desktop/pro/) installed | ||
* [Parallels Pro](https://www.parallels.com/uk/products/desktop/pro/) installed | ||
|
||
First, clone the Tracee Git repository and move into the root directory: | ||
|
||
```console | ||
git clone [email protected]:aquasecurity/tracee.git | ||
|
||
cd tracee | ||
``` | ||
|
||
Next, use Vagrant to start a Parallels VM: | ||
``` | ||
|
||
```console | ||
vagrant up | ||
``` | ||
|
||
This will use the [Vagrantfile](https://github.com/aquasecurity/tracee/blob/main/Vagrantfile) in the root of the Tracee directory. | ||
|
||
Lastly, ssh into the created VM: | ||
|
||
```console | ||
vagrant ssh | ||
``` | ||
|
||
Now, it is possible to run the Tracee Container image, using the `aarch64` tag: | ||
Now, it is possible to run the Tracee Container image: | ||
|
||
```console | ||
docker run \ | ||
--name tracee --rm -it \ | ||
--pid=host --cgroupns=host --privileged \ | ||
-v /etc/os-release:/etc/os-release-host:ro \ | ||
aquasec/tracee:aarch64 | ||
aquasec/tracee:latest | ||
``` | ||
|
||
The Tracee output should be similar to the following screenshot: | ||
|
||
![Tracee Container Image output in Vragrant on arm64](../images/docker-arm64.png) | ||
|
||
To learn how to install Tracee in a production environment, [check out the Kubernetes guide](./kubernetes-quickstart). |
Binary file not shown.