You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,39 @@ You can always run the GSW service by doing a `./gsw_service` after building. Fo
12
12
### Compatibility
13
13
Some machines do not have a /dev/shm directory. The directory used for shared memory can be changed with the flag `-shm (DIRECTORY_NAME)`. For example, `go run cmd/mem_view/mem_view.go -shm /someDirectory/RAMDrive`.
14
14
15
+
## Docker
16
+
It may be easier to run the GSW in a docker container. This might be better for compatibility and easier for people on Windows hosts (as docker desktop will natively use a WLS 2 backend).
17
+
18
+
A dockerfile for GSW is provided in `./cmd/Containerfile` and can be built and run with:
For simplicity, a `docker-compose` file is provided for building and running GSW, Grafana, and InfluxDB:
35
+
```shell
36
+
$ docker compose up --build
37
+
```
38
+
39
+
### Attaching to the container
40
+
41
+
If you need to run any of the apps in `cmd/`, you can get a shell into the container using:
42
+
```shell
43
+
$ docker exec -it gsw-service sh
44
+
```
45
+
46
+
All binaries are in PATH as the names of their folders in `cmd/`.
47
+
15
48
## Unit Tests
16
49
There are several unit tests that can be run. You can do a `go test ./...` from the root project directory to execute all tests. It is also recommended to run with the -cover
0 commit comments