@@ -103,6 +103,14 @@ jobs:
103
103
podman system reset --force
104
104
mkdir -p $HOME/.local/share/containers/storage/tmp
105
105
106
+ # start systemd user service
107
+ # since `brew services start podman` is buggy, let's do our own brew-compatible service
108
+ mkdir -p "${HOME}/.config/systemd/user/"
109
+ cp ci/cached-builds/homebrew.podman.service "${HOME}/.config/systemd/user/homebrew.podman.service"
110
+ systemctl --user daemon-reload
111
+ systemctl --user start homebrew.podman.service
112
+ echo "PODMAN_SOCK=/run/user/${UID}/podman/podman.sock" >> $GITHUB_ENV
113
+
106
114
# https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#push
107
115
- name : " push|schedule: make ${{ inputs.target }}"
108
116
run : " make ${{ inputs.target }}"
@@ -115,7 +123,7 @@ jobs:
115
123
- name : " schedule: run Trivy vulnerability scanner"
116
124
if : " ${{ fromJson(inputs.github).event_name == 'schedule' }}"
117
125
run : |
118
- TRIVY_VERSION=0.52.2
126
+ TRIVY_VERSION=0.53.0
119
127
REPORT_FOLDER=${{ github.workspace }}/report
120
128
REPORT_FILE=trivy-report.md
121
129
REPORT_TEMPLATE=trivy-markdown.tpl
@@ -126,10 +134,15 @@ jobs:
126
134
IMAGE_NAME=ghcr.io/${{ github.repository }}/workbench-images:${{ inputs.target }}-${{ github.ref_name }}_${{ github.sha }}
127
135
echo "Scanning $IMAGE_NAME"
128
136
137
+ # have trivy access podman socket,
138
+ # https://github.com/aquasecurity/trivy/issues/580#issuecomment-666423279
129
139
podman run --rm \
130
- -v $REPORT_FOLDER:/report \
140
+ -v ${PODMAN_SOCK}:/var/run/podman/podman.sock \
141
+ -v ${REPORT_FOLDER}:/report \
131
142
docker.io/aquasec/trivy:$TRIVY_VERSION \
132
143
image \
144
+ --image-src podman \
145
+ --podman-host /var/run/podman/podman.sock \
133
146
--scanners vuln,secret \
134
147
--exit-code 0 --timeout 30m \
135
148
--severity CRITICAL,HIGH \
0 commit comments