Image for cartesi machine download

[tuler]

This creates a docker image used to download cartesi machine snapshot from IPFS.
It uses the ipget go package.

This image will be used as an initContainer of a rollups node.

[endersonmaia]

pretend to use this as a workflow? if not, remove this line

Suggested change

	workflow_call:
	workflow_call:

[tuler]

Are we going to use changesets here?

This was this way because of changesets

[endersonmaia]

I'm not sure.

It won't hurt keeping it that, anyway.

[tuler]

In any case what is missing here is a release strategy, either manual tagging or changesets.

What is the strategy of helm? Manual or automated?

[endersonmaia]

For the charts/, it's automated.

Tha tags are made by the CI after the charts hits the main branch, we have a release via GH Pages, to host the helm legacy way, and also use ghcr.io for the OCI Reistry way of releasing helm charts.

I think we should deprecate the old way, and keep only the OCI Registry option.

[tuler]

So does it make sense to let changesets take control of the “landing on main”, and delegate the release to a workflow call?

[endersonmaia]

We'd have to test.

The ct tool used to release already tags, won't it conflict with the changests tagging process?

[endersonmaia]

Suggested change

	FROM debian:bookworm-20230725
	COPY --from=builder /go/bin/ipget /usr/local/bin/
	FROM debian:bookworm-20230814-slim
	COPY --from=builder /go/bin/ipget /usr/local/bin/
	RUN addgroup --system --gid 102 cartesi && \
	adduser --system --uid 102 --ingroup cartesi --disabled-login --no-create-home --home /nonexistent --gecos "cartesi user" --shell /bin/false cartesi
	USER cartesi
	ENTRYPOINT [ "ipget" ]