curben
/
blog
mirror of https://gitlab.com/curben/blog
1
0
Fork 0
Code Issues Releases Wiki Activity

docs: Add 'Snyk failed to patch in Alpine docker' post

This commit is contained in:
curben 2018-10-31 20:09:58 +10:30
parent e28e4b1f13
commit d6fb00ac76
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
source/_posts/snyk-patch-alpine-docker.md Normal file
View File

@ -0,0 +1,18 @@
---
title: Snyk failed to patch in Alpine docker
date: 2018-10-31 00:00:00
tags:
---
Snyk initially runs fine on Alpine, until you try to `snyk protect` to patch the modules. Turns out Synk depends on GNU version of `patch` utility.
<!-- more -->
Snyk is used to patch vulnerabilities of node_modules (read my [previous post]({% post_link secure-node-modules-with-snyk %}) for installation guide). I never had any issue with it running on Alpine docker image. That was because there was no modules to patch.
That is until I install [renovate](https://github.com/renovatebot/renovate), which has [vulnerabilities](https://snyk.io/test/npm/renovate) that can be patched.
Snyk only tells modules failed to patch, which is not helpful at all. I initially thought it was due to file permissions, which I now realise don't make sense. All commands are executed as root and files are owned by root.
The issue was only pinpointed after I ran snyk with `--debug`, which I should've used it in the first place anyway. The issue is due to BusyBox's patch doesn't support `--backup` option. Sigh, [BusyBox versus GNU]({% post_link gnu-vs-busybox-unix-tools %}), back at it again.
To install GNU's patch, simply add `apk add patch` before `npm install` in your CI config (e.g. `.gitlab-ci.yml`). The installation will automatically replace the BusyBox's patch symlink, so you don't need to.