4254b8688f
Update revision
/ container (push) Successful in 1m20s
2025-02-15 07:40:09 +01:00
a8c8188765
Fix path
/ container (push) Successful in 1m12s
2025-02-06 10:12:32 +01:00
d9f46a0046
Update again
/ container (push) Failing after 16s
2025-02-05 20:40:54 +01:00
83013aa0ae
Another update
2025-02-05 20:30:40 +01:00
3b3aa21be4
Try setting context
2025-02-05 20:22:01 +01:00
b47b3a22d8
Update to latest action
...
Adds a newline
2025-02-05 19:48:28 +01:00
d8be00c3ec
Update kaniko action and use new workdir
2025-02-05 19:46:14 +01:00
8d22f10c9f
Use new option for pointing out Dockerfile
2025-02-05 16:14:53 +01:00
d4a8902291
Update to new kaniko action
2025-02-05 16:13:25 +01:00
794f9c4d17
Remove working-directory
...
Did not fix anything and on closer inspection it seems this might only
be relevant when using "run".
2025-02-05 16:08:43 +01:00
4d04929b3b
Try to set working directory for kaniko
...
Currently unable to find Dockerfile:
```
Error: error resolving dockerfile path: please provide a valid path to a Dockerfile within the build context with --dockerfile
```
2025-02-05 14:29:45 +01:00
06e04be938
Try to cd into cloned dir
...
Current error:
```
Cloning into 'sunet-vcl-validator'...
fatal: reference is not a tree: 15e7af41fb56b4f19e1b6312cdd3fc697f1c0fc8
```
2025-02-05 14:24:47 +01:00
603add0f14
Use shell commands for fetching repo instead
...
Did not work as expected with the checkout action (it is trying to use
auth etc).
2025-02-05 14:21:36 +01:00
770bb08547
Workflow for building container from github repo
2025-02-05 13:20:42 +01:00
