We need a way to simplify pull from `quay.io/tinkerbell-actions`, the
location for the reusable actions we release.
https://artifacthub.io/packages/search?kind=4
All the images are proxies via an internal registry. This commit
configures it to look at the images hosted in
`quay.io/tinkerbell-actions` when there is not one in the internal
registry and it proxies.
For example:
$ docker pull 192.168.1.1/tinkerbell-actions/rootio:v1.0.0
v1.0.0: Pulling from tinkerbell-actions/rootio
b5b0f03f0cb8: Pull complete
48742f086697: Pull complete
06d27b65800a: Pull complete
3281556401c6: Pull complete
b94e835dc9fd: Pull complete
Digest: sha256:ec9855556388a690cad2535cf813f69cffa6df24476aedb16b3cdfc0d809492c
Status: Downloaded newer image for 192.168.1.1/tinkerbell-actions/rootio:v1.0.0
192.168.1.1/tinkerbell-actions/rootio:v1.0.0
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
As I explained here
https://github.com/tinkerbell/sandbox/pull/66#issuecomment-803009169 the
current OSIE on master broke how tink-worker gets installed in sandbox.
For a series of bad habits the PR got merged even if e2e tests are
broken leaving sandbox/master to a not working state
This commit reverts OSIE back to a fully operational version
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
Apparently the idea to prefix a package with an underscore is not that
smart as I thought. Yes `go test` does not run it by default when you
run `go test ./...` but also other commands like `go mod tidy` do not
work consistently.
Nothing changes in practice. By default only unit tests run. Setting the
new environment variable: `TEST_WITH_VAGRANT` you include the test who
uses vagrant.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
I am not sure when it happens, it can be when we removed the NGINX_IP,
or when we checked that every services were using ports OR network_mode
but we exposed nginx and boots over the same port.
This commit fixes that.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
This commit contains a new utility that helps to automate a version bump
for sandbox.
You can run this command to get the vibe of what it does.
```
$ go run cmd/bump-version/main.go -help
```
In order to try it out you can run this command form sandbox root. By
default it won't overwrite anything. It will print to stdout a new
version of the current_versions.sh file where all the images are
calculate cloning the various repositories
```
$ go run cmd/bump-version/main.go
```
If you want to overwrite the current_versions file you can use the flag
`-overwrite`.
More will come but for now, that's the PoC. Ideally this can be hooked
to CI/CD and run periodically, opening a PR that can be evaluated and
merged.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
The go program we use to get binaries from a docker image was unpacking
only the last layer. This is not required and it order to have a more
generic approach and fewest requirement the program now unpack all the
image
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
The main reason for this bump is because we fixed multi arch support for
boots binaries. Before docker images were multi arch but boots was
always x86. This issue is not fixed.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
script/release-binaries.sh
When writing the release-binary bash script I didn't use the right
variables in current_versions.sh but I fixed those values as part of the
script itself.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
have a look at the README.md to see how it works.
Bootstrap a CLI program to copy binaries from multi arch images
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
Tinkerbell is made of different components as we all know at this point.
Sandbox had those versions all over the places. This PR moves them as
part of the `envrc` file.
Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
Gianluca Arbezzano