cerc-io/stack-orchestrator
Archived
12
1
Fork 3
Code Issues 117 Pull Requests 25 Actions Packages Projects Releases 493 Wiki Activity

Rename containers to cerc-io #79

New Issue
Open
opened 2022-12-21 03:43:44 +00:00 by dboreham · 6 comments
dboreham commented 2022-12-21 03:43:44 +00:00
Contributor
Copy Link
Copy Source

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
Author
Contributor
Copy Link
Copy Source

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
Member
Copy Link
Copy Source

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
Author
Contributor
Copy Link
Copy Source

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
Author
Contributor
Copy Link
Copy Source

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
Author
Contributor
Copy Link
Copy Source

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
Member
Copy Link
Copy Source

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.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
K8s
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 in progress
invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
Copied from Github
An issue or PR manually copied from GitHub.
 Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
AFDudley Alex ashwin cerccicd ericlewis i-norden (Ian Norden) prathamesh (Prathamesh Musale) rachmaninovquar rjk-laconic roysc (Roy Crihfield) srw zramsay
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#79