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

failed to build ds-idrepo image with skaffold #678

Open
Hannoto opened this issue Dec 6, 2023 · 0 comments
Open

failed to build ds-idrepo image with skaffold #678

Hannoto opened this issue Dec 6, 2023 · 0 comments

Comments

@Hannoto
Copy link

Hannoto commented Dec 6, 2023

Hi, Im try to bring up FR 7.1 (tried with 7.4 too) base on this docs on GKE reside at GCP, but the process keep failing event after few time execution. The console logs:

MacBook-Pro forgeops % skaffold debug --profile small
Generating tags...

  • am -> gcr.io/prj-labs-coms110a8a/am:8bf3568c1
  • amster -> gcr.io/prj-labs-coms110a8a/amster:3cef63255
  • idm -> gcr.io/prj-labs-coms110a8a/idm:a55f38bd5
  • ds-cts -> gcr.io/prj-labs-coms110a8a/ds-cts:4c74d1834
  • ds-idrepo -> gcr.io/prj-labs-coms110a8a/ds-idrepo:4c74d1834
  • ig -> gcr.io/prj-labs-coms110a8a/ig:81f8b9db3
  • ds -> gcr.io/prj-labs-coms110a8a/ds:5a524c268
    Checking cache...
  • am: Found Remotely
  • amster: Found Remotely
  • idm: Found Remotely
  • ds-cts: Found Remotely
  • ds-idrepo: Not found. Building
  • ig: Found Remotely
  • ds: Found Remotely
    Starting build...
    Building [ds-idrepo]...
    Target platforms: [linux/amd64]
    #0 building with "desktop-linux" instance using docker driver

#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s

#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 2.41kB done
#2 DONE 0.0s

#3 [internal] load metadata for gcr.io/forgerock-io/ds:7.4.0
#3 DONE 0.7s

#4 [ 1/10] FROM gcr.io/forgerock-io/ds:7.4.0@sha256:4aa4549e76366c63b718ee340b7e95ac29467cb51b61507288c0992501c13434
#4 DONE 0.0s

#5 [internal] load build context
#5 transferring context: 1.19kB done
#5 DONE 0.0s

#6 [ 2/10] COPY debian-buster-sources.list /etc/apt/sources.list
#6 CACHED

#7 [ 8/10] COPY --chown=forgerock:root idrepo/*.ldif /var/tmp/
#7 CACHED

#8 [ 5/10] COPY --chown=forgerock:root idrepo /opt/opendj/
#8 CACHED

#9 [ 6/10] COPY --chown=forgerock:root scripts /opt/opendj/scripts
#9 CACHED

#10 [ 7/10] COPY --chown=forgerock:root uma /opt/opendj/uma
#10 CACHED

#11 [ 3/10] WORKDIR /opt/opendj
#11 CACHED

#12 [ 4/10] COPY --chown=forgerock:root common /opt/opendj/
#12 CACHED

#13 [ 9/10] RUN chmod +w template/setup-profiles/AM/config/6.5/base-entries.ldif && cat scripts/external-am-datastore.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && cat uma/opendj_uma_audit.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && cat uma/opendj_uma_pending_requests.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && cat uma/opendj_uma_resource_set_labels.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && cat uma/opendj_uma_resource_sets.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && cat /var/tmp/alpha_bravo.ldif >> template/setup-profiles/AM/config/6.5/base-entries.ldif && chmod +w template/setup-profiles/AM/identity-store/7.0/base-entries.ldif && cat /var/tmp/orgs.ldif >> template/setup-profiles/AM/identity-store/7.0/base-entries.ldif && rm /var/tmp/*ldif
#13 CACHED

#14 [10/10] RUN bin/setup.sh && bin/relax-security-settings.sh && rm bin/setup.sh bin/relax-security-settings.sh
#14 13.50
#14 13.51 Configuring profile AM configuration data store..........Error......
#14 30.22 The 'AM configuration data store' setup profile failed: Unable to import data
#14 30.22 (tool exit with error return code '1')
#14 30.22 See /tmp/opendj-setup-profile-8589934804087545949.log for a detailed log of
#14 30.22 the failed operation.
#14 30.22 Please report this error and provide the log file mentioned above.
#14 35.99 create-trust-manager-provider --provider-name "PEM Trust Manager" --type pem --set enabled:true --set pem-directory:pem-trust-directory
#14 39.41
#14 39.41 The Pem Trust Manager Provider was created successfully
#14 39.42
#14 39.43 set-connection-handler-prop --handler-name https --set trust-manager-provider:"PEM Trust Manager"
#14 40.53
#14 40.53 set-connection-handler-prop --handler-name ldap --set trust-manager-provider:"PEM Trust Manager"
#14 41.17
#14 41.17 set-connection-handler-prop --handler-name ldaps --set trust-manager-provider:"PEM Trust Manager"
#14 41.64
#14 41.64 set-synchronization-provider-prop --provider-name "Multimaster Synchronization" --set trust-manager-provider:"PEM Trust Manager"
#14 42.11
#14 42.11 set-administration-connector-prop --set trust-manager-provider:"PEM Trust Manager"
#14 42.56
#14 42.57 delete-trust-manager-provider --provider-name "PKCS12"
#14 43.63
#14 43.64 The Trust Manager Provider was deleted successfully
#14 43.64
#14 43.71 create-key-manager-provider --provider-name "PEM Key Manager" --type pem --set enabled:true --set pem-directory:pem-keys-directory
#14 45.13
#14 45.13 The Pem Key Manager Provider was created successfully
#14 45.13
#14 45.13 set-connection-handler-prop --handler-name https --set key-manager-provider:"PEM Key Manager"
#14 45.53
#14 45.53 set-connection-handler-prop --handler-name ldap --set key-manager-provider:"PEM Key Manager"
#14 45.84
#14 45.84 set-connection-handler-prop --handler-name ldaps --set key-manager-provider:"PEM Key Manager"
#14 46.25
#14 46.25 set-synchronization-provider-prop --provider-name "Multimaster Synchronization" --set key-manager-provider:"PEM Key Manager"
#14 46.59
#14 46.59 set-crypto-manager-prop --set key-manager-provider:"PEM Key Manager"
#14 46.90
#14 46.90 set-administration-connector-prop --set key-manager-provider:"PEM Key Manager"
#14 47.23
#14 47.23 delete-key-manager-provider --provider-name "PKCS12"
#14 47.81
#14 47.81 The Key Manager Provider was deleted successfully
#14 47.81
#14 47.81 create-backend-index --backend-name amIdentityStore --set index-type:equality --type generic --index-name fr-idm-uuid
#14 48.14
#14 48.14 The parent Pluggable Backend does not exist
#14 48.14
#14 ERROR: process "/bin/sh -c bin/setup.sh && bin/relax-security-settings.sh && rm bin/setup.sh bin/relax-security-settings.sh" did not complete successfully: exit code: 32

[10/10] RUN bin/setup.sh && bin/relax-security-settings.sh && rm bin/setup.sh bin/relax-security-settings.sh:
46.90 set-administration-connector-prop --set key-manager-provider:"PEM Key Manager"
47.23
47.23 delete-key-manager-provider --provider-name "PKCS12"
47.81
47.81 The Key Manager Provider was deleted successfully
47.81
47.81 create-backend-index --backend-name amIdentityStore --set index-type:equality --type generic --index-name fr-idm-uuid
48.14
48.14 The parent Pluggable Backend does not exist
48.14


Dockerfile:40

39 |
40 | >>> RUN bin/setup.sh &&
41 | >>> bin/relax-security-settings.sh &&
42 | >>> rm bin/setup.sh bin/relax-security-settings.sh
43 |

ERROR: failed to solve: process "/bin/sh -c bin/setup.sh && bin/relax-security-settings.sh && rm bin/setup.sh bin/relax-security-settings.sh" did not complete successfully: exit code: 32
Cleaning up...

  • No resources found
    build [ds-idrepo] failed: exit status 1. Docker build ran into internal error. Please retry.
    If this keeps happening, please open an issue..

How I can fix this issue?
My laptop running on M1 processor.

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

No branches or pull requests

1 participant