Rename containers to cerc-io #79

New Issue

dboreham · 2022-12-21T03:43:44Z

dboreham commented

2022-12-21 03:43:44 +00:00

When stack-orchestrator was written, there were no cerc container images and we used tags like cerc/container-name.
However in the meantime other folks began building container images and naming them cerc-io/container-name so we need to rename all ours.

When stack-orchestrator was written, there were no cerc container images and we used tags like `cerc/container-name`. However in the meantime other folks began building container images and naming them `cerc-io/container-name` so we need to rename all ours.

dboreham commented

2023-01-06 23:15:12 +00:00

Confirm we really do already ship containers in the cerc-io domain because I can't find any on https://git.vdb.to/cerc-io/-/packages

Confirm we really do already ship containers in the `cerc-io` domain because I can't find any on https://git.vdb.to/cerc-io/-/packages

zramsay commented

2023-10-17 21:14:15 +00:00

ah yeah, i was getting error parsing HTTP 404 response body: invalid character 'N' looking for beginning of value: "Not found.\n" from a docker push because the container name used cerc instead of cerc-io, the latter being the org on gitea which needs to be same in the container name

ah yeah, i was getting `error parsing HTTP 404 response body: invalid character 'N' looking for beginning of value: "Not found.\n"` from a `docker push` because the container name used `cerc` instead of `cerc-io`, the latter being the org on gitea which needs to be same in the container name

dboreham commented

2023-10-18 03:03:21 +00:00

Hmm. Did gitea change this recently, because we definitely have published images with cerc like : https://git.vdb.to/cerc-io/-/packages/container/cerc%2Flighthouse-cli/test

Hmm. Did gitea change this recently, because we definitely have published images with `cerc` like : https://git.vdb.to/cerc-io/-/packages/container/cerc%2Flighthouse-cli/test

dboreham commented

2023-10-18 03:04:38 +00:00

Although....the tag seems to get mangled like : docker pull git.vdb.to/cerc-io/cerc/lighthouse-cli:test and docker pull git.vdb.to/cerc-io/laconicd/laconicd:v0.8.0

Although....the tag seems to get mangled like : `docker pull git.vdb.to/cerc-io/cerc/lighthouse-cli:test` and `docker pull git.vdb.to/cerc-io/laconicd/laconicd:v0.8.0`

dboreham commented

2023-10-18 03:07:04 +00:00

I think those docker pull URLs are ok though -- git.vdb.to/cerc-io/ is the repository path, while cerc/lighthouse-cli:test is the container tag (I think, based on looking at other non-cerc images we published there).

I _think_ those docker pull URLs are ok though -- `git.vdb.to/cerc-io/` is the repository path, while `cerc/lighthouse-cli:test` is the container tag (I think, based on looking at other non-cerc images we published there).

zramsay commented

2023-10-18 14:30:55 +00:00

ah my mistake, what i was calling "container name" i meant "container user", i.e.,

git.vdb.to/cerc-io/ works but git.vdb.to/cerc/ doesn't. That our containers are still named cerc locally makes encountering this more likely.git.vdb.to/cerc-io/cerc definitely will work. It's not a gitea issue.

ah my mistake, what i was calling "container name" i meant "container user", i.e., `git.vdb.to/cerc-io/` works but `git.vdb.to/cerc/` doesn't. That our containers are still named `cerc` locally makes encountering this more likely.`git.vdb.to/cerc-io/cerc` definitely will work. It's not a gitea issue.

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#79