Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose.yml: pull access denied for fargeo/aher6-2 #1346

Open
PaulJWright opened this issue Nov 12, 2024 · 4 comments
Open

docker-compose.yml: pull access denied for fargeo/aher6-2 #1346

PaulJWright opened this issue Nov 12, 2024 · 4 comments

Comments

@PaulJWright
Copy link

Hello,

I am trying to spin up the docker container w/ docker compose, and I am being denied pull access for fargeo/aher6-2. Is there a private container registry I need details for?

➜  arches-her git:(master) docker compose up
WARN[0000] /Users/paulwright/Documents/work/RICHeS/arches-her/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/1
 ! aher Warning pull access denied for fargeo/aher6-2, repository does not exist or may require 'docker login': denied: requested access to the resource is denied                                                 10.2s
[+] Building 0.0s (0/0)
@aj-he
Copy link
Collaborator

aj-he commented Nov 12, 2024

Hi @PaulJWright - please try using branch dev/1.0.x

UPDATED: The Readme in this branch should provide info on using the docker configuration

@PaulJWright
Copy link
Author

PaulJWright commented Dec 12, 2024

Hi @aj-he, apologies for not getting back to you. This worked, thank you.

What is the justification behind building from dev/1.0.x and not main or a later dev branch? We are considering Arches and Arches-her as a potential platform, and would like to build the latest version

EDIT: Apologies, just seen the update!

@aj-he
Copy link
Collaborator

aj-he commented Dec 12, 2024

@PaulJWright yeah, using a "dev/" branch as the current working branch is a bit unusual. It's a pattern being used by the core Arches team to manage LTS and latest versions. The core team set the latest dev branch as default, but arches-her hasn't done this yet. Probably should!

@PaulJWright
Copy link
Author

@PaulJWright yeah, using a "dev/" branch as the current working branch is a bit unusual. It's a pattern being used by the core Arches team to manage LTS and latest versions. The core team set the latest dev branch as default, but arches-her hasn't done this yet. Probably should!

This makes sense. I think I was confused by dev/1.0.x and dev/7.0.x dev/7.1.x etc, but I presume dev/1.0.x is an arches-her version, whereas 5/6/7.x.x are related to the core arches version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants