You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi, I recently had some issues with the "/etc/core/token" mount called "psc" in the bitnami/helm chart, and I'm trying to trace it to the source. I suspect the lines below are the origin of this mount.
I've tested the helm chart with the mount removed, and it seems to work perfectly fine without it. I tried looking for the origin, saw it in the goharbor/harbor-helm chart and then also here in the test data. Then I tried searching the code to figure out what interacts with this mount, but I can't find anything. I would love to know if the removal of the mount is breaking something and if yes, what.
BTW, my original error that caused this search was this:
Error: container create failed: creating /etc/core/token: openat2 "etc/core/token": No such file or directory
This is what I got on my microshift instance. Without the mount in the container, everything is working.
Describe the solution you'd like
I would love to know if this mount is really needed or not, so that I or someone else can submit a patch to remove it or realize my error and go back to debugging, now with new motivation due to the consequences of this mount missing.
Thanks in advance for any input regarding this.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi, I recently had some issues with the "/etc/core/token" mount called "psc" in the bitnami/helm chart, and I'm trying to trace it to the source. I suspect the lines below are the origin of this mount.
harbor/src/pkg/chart/testdata/harbor-schema1/templates/core/core-dpl.yaml
Lines 181 to 182 in fef9524
harbor/src/pkg/chart/testdata/harbor-schema2/templates/core/core-dpl.yaml
Lines 181 to 182 in fef9524
I've tested the helm chart with the mount removed, and it seems to work perfectly fine without it. I tried looking for the origin, saw it in the goharbor/harbor-helm chart and then also here in the test data. Then I tried searching the code to figure out what interacts with this mount, but I can't find anything. I would love to know if the removal of the mount is breaking something and if yes, what.
BTW, my original error that caused this search was this:
This is what I got on my microshift instance. Without the mount in the container, everything is working.
Describe the solution you'd like
I would love to know if this mount is really needed or not, so that I or someone else can submit a patch to remove it or realize my error and go back to debugging, now with new motivation due to the consequences of this mount missing.
Thanks in advance for any input regarding this.
The text was updated successfully, but these errors were encountered: