Skip to main content
P
PG_100830575-Regular Member
5-Regular Member
December 31, 2022
Solved

Trying to create the security image but, in the documentation there is an impossible command shell

  • December 31, 2022
  • 1 reply
  • 2198 views

Hi @VladimirRosu_116627, I'm trying to create the security image but as you can see, in the documentation there is an impossible command shell, without param.

I didn't find the meaning going through the sh code. 

maybe I missed something

PG_10083057_0-1672508185555.png

this is the error trying to create the  twx image

PG_10083057_1-1672508557937.png

Thanks in advance

Pier

 

Best answer by jensc

Hello,

 

For your particular error: "Failed to create SecurityManager, Failed to load SecretProvider".

I found this PTC support page: https://www.ptc.com/en/support/article/CS305796

It goes into detail on what you could try to fix the issue.

 

Regards,

Jens

1 reply

J
jensc17-Peridot
17-Peridot
January 2, 2023

Hello,

 

The error message in your second screenshot gives me the impression that you do not have permission to access the docker images.

Are the images located locally on your computer or are you trying to pull them from a remote registry?

 

Regards,

Jens

 

 

P
PG_100830575-Regular MemberAuthor
5-Regular Member
January 3, 2023

Hi Jens! Thanks for your reply.

I think I fix that and the state of art is:

Security container: OK!

PG_10083057_0-1672748137910.png

PostgreS: OK!

PG_10083057_1-1672748197854.pngPG_10083057_2-1672748239169.png

 

Platform: KO!

Thoughts?

PG_10083057_3-1672748325057.png

J
jensc17-Peridot
17-Peridot
January 3, 2023

Hello,

 

It is a bit hard to tell. But it looks like you are getting an error in your Postgres logs, although it does also say the initialization was completed...

For you platform it does look like there is something wrong with your security-cli. Might be because of the password.

 

I have attached my yaml file, I was using a MSSQL DB, but I hope you can still compare it to yours.

 

I know I had some issues with the security stuff as well and I think it was because I was missing something in the yaml file relating to the KEYSTORE.

 

Hope it helps you.

 

Regards,

Jens

Terms & ConditionsCookie settingsAccessibility statement