all the docker images used in this flow should be pre-built and the instruction should pull them from the gitea registry #13

New Issue

zramsay · 2024-07-25T14:20:45Z

zramsay commented

2024-07-25 14:20:45 +00:00

No description provided.

dboreham commented

2024-07-25 14:52:59 +00:00

I created a repo to host the laconicd stacks (no stack content there yet -- it seems to be spread around in various places and needs to be cleaned up), but it has a CI job to publish the fixturenet images. This can be copied to make a job to publish images for other variants of laconicd stacks.

The images are published: https://git.vdb.to/cerc-io/-/packages/container/cerc%2Flaconicd/202407251447

Beware the container image registry scheme we have now is pretty simplistic and will not behave well if two people publish images with the same name that are in fact for different purposes. Basically the container image name is global. So if you do something funky with an image, change the name.

I created a [repo ](https://git.vdb.to/cerc-io/laconicd-stacks)to host the laconicd stacks (no stack content there yet -- it seems to be spread around in various places and needs to be cleaned up), but it has a [CI job](https://git.vdb.to/cerc-io/laconicd-stacks/actions?workflow=publish-fixturenet-laconicd-images.yml&actor=0&status=0) to publish the fixturenet images. This can be copied to make a job to publish images for other variants of laconicd stacks. The images are published: https://git.vdb.to/cerc-io/-/packages/container/cerc%2Flaconicd/202407251447 Beware the container image registry scheme we have now is pretty simplistic and will not behave well if two people publish images with the same name that are in fact for different purposes. Basically the container image name is global. So if you do something funky with an image, change the name.

Sign in to join this conversation.