Date   

Error pushing images

Ignazio Cassano
 

Hello Everyone,
After the first installation of harbor with an external redis and an external DB and with registry on S3, I pushed an images alpine:latest
Then I removed harbor and installed it again.
I tried to push again the same image and I got:

unknown: http status code: 404, body: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Name":"primoproj/alpine","Revision":"sha256:1304f174557314a7ed9eddb4eab12fed12cb0cd9809e4c28f29af86979a3c870"}}]}

If I try to push a new image that I never pushed before, it works.
Any help, please ?
Ignazio


Re: Amozon s3 for registry

Ignazio Cassano
 

Many thanks
Ignazio

Il Gio 22 Set 2022, 01:13 daojunz via lists.cncf.io <daojunz=vmware.com@...> ha scritto:

You could refer this configure file

https://github.com/distribution/distribution/blob/main/docs/configuration.md

 

  s3:

    accesskey: awsaccesskey

    secretkey: awssecretkey

    region: us-west-1

    regionendpoint: http://myobjects.local

    forcepathstyle: true

    accelerate: false

    bucket: bucketname

    encrypt: true

    keyid: mykeyid

    secure: true

    v4auth: true

    chunksize: 5242880

    multipartcopychunksize: 33554432

    multipartcopymaxconcurrency: 100

    multipartcopythresholdsize: 33554432

    rootdirectory: /s3/object/name/prefix

    usedualstack: false

 

The option in red text is mandatory

 

Best regards,

Stone (张道军)

Software Engineer, CNA, VMware R&D

 

-- 

 

 

From: harbor-users@... <harbor-users@...> on behalf of Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
Date: Wednesday, September 21, 2022 at 10:42 PM
To: harbor-users@... <harbor-users@...>
Subject: [harbor-users] Amozon s3 for registry

Hello,

I would like to use S3 for registry.

In values.yaml of harbor I wrote:

 

region: eu-central-1
          bucket: ignaharbor
          accesskey: myaccesskey
          secretkey: mysecret

 

Is this enough to work ?

 

Thanks

Ignazio

 



Re: Amozon s3 for registry

daojunz
 

You could refer this configure file

https://github.com/distribution/distribution/blob/main/docs/configuration.md

 

  s3:

    accesskey: awsaccesskey

    secretkey: awssecretkey

    region: us-west-1

    regionendpoint: http://myobjects.local

    forcepathstyle: true

    accelerate: false

    bucket: bucketname

    encrypt: true

    keyid: mykeyid

    secure: true

    v4auth: true

    chunksize: 5242880

    multipartcopychunksize: 33554432

    multipartcopymaxconcurrency: 100

    multipartcopythresholdsize: 33554432

    rootdirectory: /s3/object/name/prefix

    usedualstack: false

 

The option in red text is mandatory

 

Best regards,

Stone (张道军)

Software Engineer, CNA, VMware R&D

 

-- 

 

 

From: harbor-users@... <harbor-users@...> on behalf of Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
Date: Wednesday, September 21, 2022 at 10:42 PM
To: harbor-users@... <harbor-users@...>
Subject: [harbor-users] Amozon s3 for registry

Hello,

I would like to use S3 for registry.

In values.yaml of harbor I wrote:

 

region: eu-central-1
          bucket: ignaharbor
          accesskey: myaccesskey
          secretkey: mysecret

 

Is this enough to work ?

 

Thanks

Ignazio

 



Terraform Harbor Provider looking for maintainers

Orlin Vasilev
 

Hi all  :)


In that issue we are asking for help if you are feeling like sparing some time and you know terraform or you want to use that to learn terraform and to join our project in general :)

Please reach out to us so we can work on this one together!

Orlix
Harbor Community Manager


Re: Amozon s3 for registry

Ignazio Cassano
 

Hello, I tried to push an image but in registry logs, it give me the following error:

Il giorno mer 21 set 2022 alle ore 16:42 Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...> ha scritto:

Hello,
I would like to use S3 for registry.
In values.yaml of harbor I wrote:

region: eu-central-1
          bucket: ignaharbor
          accesskey: myaccesskey
          secretkey: mysecret

Is this enough to work ?

Thanks
Ignazio


Amozon s3 for registry

Ignazio Cassano
 

Hello,
I would like to use S3 for registry.
In values.yaml of harbor I wrote:

region: eu-central-1
          bucket: ignaharbor
          accesskey: myaccesskey
          secretkey: mysecret

Is this enough to work ?

Thanks
Ignazio


Re: harbor multi site

Ignazio Cassano
 

Thanks for your answer.
Please, could you explain a fallback scenario ?
Ignazio

Il giorno mar 20 set 2022 alle ore 10:39 Vadim Bauer via lists.cncf.io <vb=container-registry.com@...> ha scritto:

It's possible to use replication as a way to back up images, but in practice it is not usable.

The main reason is that when you switch sites, you would need to rotate all pull secrets for every consumer of your registry.

A usable fallback scenario is a bit more complicated than that and depends on the given infrastructure. 


Re: harbor multi site

Vadim Bauer
 

It's possible to use replication as a way to back up images, but in practice it is not usable.

The main reason is that when you switch sites, you would need to rotate all pull secrets for every consumer of your registry.

A usable fallback scenario is a bit more complicated than that and depends on the given infrastructure. 


harbor multi site

Ignazio Cassano
 

Hello Everyone,
I would like to install 3 harbor each one on a different site: harbor 1 on Site A, harbor 2 on Site B and harbor 3 on Site C.
To keep them aligned I would like to use harbor replication but only one can push.
I wonder if an haproxy load balancer can check which harbor installation is  pushing (so which is the master). This because the master could fail and I could switch one of the 2 remained in pushing mode.
Thanks
Ignazio


Re: goharbor

Ignazio Cassano
 

Hello, thanks for your answer
The following are my values for external redis:

 external:
        # support redis, redis+sentinel
        # addr for redis: <host_redis>:<port_redis>
        # addr for redis+sentinel: <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
        addr: "haproxy-harbor:6379"
        # The name of the set of Redis instances to monitor, it must be set to support redis+sentinel
        sentinelMasterSet: ""
        # The "coreDatabaseIndex" must be "0" as the library Harbor
        # used doesn't support configuring it
        coreDatabaseIndex: "0"
        jobserviceDatabaseIndex: "1"
        registryDatabaseIndex: "2"
        chartmuseumDatabaseIndex: "3"
        trivyAdapterIndex: "5"
        password: "password"
        # If using existingSecret, the key must be REDIS_PASSWORD
        existingSecret: ""


Il giorno lun 19 set 2022 alle ore 13:25 Orlin Vasilev <orlin@...> ha scritto:
Hi Ignazio,

can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)

Orlix

On Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:

Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>

12:06 (9 minuti fa)
   
 
Hello All,
I am trying to setup goarbor with external redis but it does not work:
 
2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.
 
The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio


Re: goharbor

Ignazio Cassano
 

Hello, thanks for your answer.
The following are the redix external values:

 external:
        # support redis, redis+sentinel
        # addr for redis: <host_redis>:<port_redis>
        # addr for redis+sentinel: <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
        addr: "haproxy-harbor:6379"
        # The name of the set of Redis instances to monitor, it must be set to support redis+sentinel
        sentinelMasterSet: ""
        # The "coreDatabaseIndex" must be "0" as the library Harbor
        # used doesn't support configuring it
        coreDatabaseIndex: "0"
        jobserviceDatabaseIndex: "1"
        registryDatabaseIndex: "2"
        chartmuseumDatabaseIndex: "3"
        trivyAdapterIndex: "5"
        password: "********"
        # If using existingSecret, the key must be REDIS_PASSWORD
        existingSecret: ""



Il giorno lun 19 set 2022 alle ore 13:58 Wenkai Yin <yinw@...> ha scritto:

Hi lgnazio, this is a known issue and already fixed. The fix should be available in the next patch release v1.10.1 of Harbor helm chart, or you can patch the Harbor helm chart with the same change in the fix.

 

Regards,

Wenkai

From: harbor-users@... <harbor-users@...> on behalf of Orlin Vasilev via lists.cncf.io <orlin=orlix.org@...>
Date: Monday, September 19, 2022 at 19:25
To: harbor-users@... <harbor-users@...>
Subject: Re: [harbor-users] goharbor

Hi Ignazio,

 

can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)

 

Orlix

 

On Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:

Image removed by sender.

Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>

12:06 (9 minuti fa)

 

 

 

 

Hello All,

I am trying to setup goarbor with external redis but it does not work:

 

2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.

 

The password I inserted in values.yaml is correct but seems user is hardcoded.

Please, help me

Ignazio

 



Re: goharbor

yinw
 

Hi lgnazio, this is a known issue and already fixed. The fix should be available in the next patch release v1.10.1 of Harbor helm chart, or you can patch the Harbor helm chart with the same change in the fix.

 

Regards,

Wenkai

From: harbor-users@... <harbor-users@...> on behalf of Orlin Vasilev via lists.cncf.io <orlin=orlix.org@...>
Date: Monday, September 19, 2022 at 19:25
To: harbor-users@... <harbor-users@...>
Subject: Re: [harbor-users] goharbor

Hi Ignazio,

 

can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)

 

Orlix

 

On Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:

Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>

12:06 (9 minuti fa)

 

 

 

 

Hello All,

I am trying to setup goarbor with external redis but it does not work:

 

2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.

 

The password I inserted in values.yaml is correct but seems user is hardcoded.

Please, help me

Ignazio

 



Re: goharbor

Orlin Vasilev
 

Hi Ignazio,

can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)

Orlix

On Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:

Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>

12:06 (9 minuti fa)
   
 
Hello All,
I am trying to setup goarbor with external redis but it does not work:
 
2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.
 
The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio


goharbor

Ignazio Cassano
 

Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>

12:06 (9 minuti fa)
   
 
Hello All,
I am trying to setup goarbor with external redis but it does not work:
 
2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.
 
The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio


goharbor redis user harcoded

Ignazio Cassano
 

Hello All,
I am trying to setup goarbor with external redis but it does not work:

2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.

The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio


Re: Harbor 2.5.2 is out!

Orlin Vasilev
 

 Sent too soon: (fat fingers)

and:
zyyw 
YangJiao0817

Thank you folks!

Orlix

On Fri, Jul 1, 2022 at 11:53 AM Orlin Vasilev via lists.cncf.io <orlin=orlix.org@...> wrote:
Hi all,

Well, we know Friday is not the best day for updates but we have some fixes that need your attention :)

Release 2.5.2 is out and you can check all changes and updates here:


Thank you for all Issues/PR/Slack messages and contributions in general!

Especially to :
wy65701436
chlins
stonezdj

Orlix
Harbor Community Manager

Happy upgrading!
...or maybe on Monday


Harbor 2.5.2 is out!

Orlin Vasilev
 

Hi all,

Well, we know Friday is not the best day for updates but we have some fixes that need your attention :)

Release 2.5.2 is out and you can check all changes and updates here:


Thank you for all Issues/PR/Slack messages and contributions in general!

Especially to :
wy65701436
chlins
stonezdj

Orlix
Harbor Community Manager

Happy upgrading!
...or maybe on Monday


[CNCF] Greetings from Singapore

Turritopsis Dohrnii Teo En Ming
 

Subject: [CNCF] Greetings from Singapore

Hi!

My name is Mr. Turritopsis Dohrnii Teo En Ming.

I am a Targeted Individual (TI) living in Singapore.

I am also an IT Consultant with a Systems Integrator (SI) in Singapore.

Just a short intro :)


Re: KubeCon NA 22 -CfP is closing soon!

Orlin Vasilev
 

Hi all good news here :) CNCF extended the deadline until 3th of June :) 


On Mon, May 23, 2022 at 10:21 AM Orlin Vasilev <orlin@...> wrote:
Hi All,
Reminder that CfP is closing on 27th of May:

Please submit your talks before that!
If you need any help with submitting or you need a stage buddy I'm here to help!

I'll be super happy to join everyone on stage or support you in your talk in any way!

The benefits of having a talk:
- free ticket for KubeCon
- recognized as Speaker - special swag/media/parties
- make yourself more recognizable
- meet one of the best in the field
etc..

I think we have a LOT to show at such a conference so please think about it and drop a line!
If nobody files a talk I'll do one! We must be there as a community! :)

Orlix
Harbor Community Manager


KubeCon NA 22 -CfP is closing soon!

Orlin Vasilev
 

Hi All,
Reminder that CfP is closing on 27th of May:

Please submit your talks before that!
If you need any help with submitting or you need a stage buddy I'm here to help!

I'll be super happy to join everyone on stage or support you in your talk in any way!

The benefits of having a talk:
- free ticket for KubeCon
- recognized as Speaker - special swag/media/parties
- make yourself more recognizable
- meet one of the best in the field
etc..

I think we have a LOT to show at such a conference so please think about it and drop a line!
If nobody files a talk I'll do one! We must be there as a community! :)

Orlix
Harbor Community Manager