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
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,12 +67,11 @@ docker run \
67
67
A few notes on this docker run call:
68
68
69
69
- We run the container without root privileges as user `nonroot`. This user is defined in the Wolfi base image.
70
-
-`config.yml` and `ssh_key.pem` specify the configuration. `config.yml` is mounted as volume, whereas the content of `ssh_key.epm`
70
+
-`config.yml` and `ssh_key.pem` specify the configuration. `config.yml` is mounted as volume, whereas the content of `ssh_key.pem`
71
71
is passed as environment variable `SSH_PRIVATE_KEY`. This is to prevent from permission issues. The ssh key is for git interaction with the
72
-
remote repository specified in the config file. Of course it needs to be already known to the git repo.
73
-
- The local git working folder would preferably also be mounted into the container so its contents could be cached between container runs.
74
-
But this seems not to be possible -- at least not without administrational permission on the host machine. The issue is that mounted
75
-
volumes always belong to root, but the container does not run with root permissions, so it has no write access to the folder.
72
+
remote repository specified in the config file. Of course the key already needs to be registered with the git repo.
73
+
- As an alternative to access git via `ssh`, it's also possible to use the `https` protocol. In this case you will need to create a
74
+
personal access token in the github user interface to gain write access to the middleware repo. This access token is passed in terms of the environment variable `ACCESS_TOKEN`.
0 commit comments