E:\VMware\PortalRuntimeFile\PortalRuntime>load.bat E:\VMware\PortalRuntimeFile\hcl-dx-kubernetes-v95-CF197
Loaded image: hcl/dx/content-composer:v1.10.0_20210806-1258
Loaded image: hcl/dx/image-processor:v1.10.0_20210806-1300
Loaded image: hcl/dx/postgres:v1.10.0_20210806-1302
Error processing tar file(exit status 1): archive/tar: invalid tar header
Loaded image: hcl/dx/ringapi:v1.10.0_20210806-1311
Error processing tar file(gzip: invalid checksum):
"Updating properties file with image tags"
此时不应有 (。

E:\VMware\PortalRuntimeFile\PortalRuntime>

I failed in loading images to my docker desktop . error log is above.

I am running DX locally on Docker Desktopp with localhost as hostname.

1. Here is what I am seeing when I access DAM -
   Request URL:
   http://localhost:10039/dx/api/core/v1/dxmyrest/access/current-user?resourceId=wps.MEDIA_LIBRARY
   Request Method:
   GET
   Status Code:
   404 Not Found
   Remote Address:
   [::1]:10039
   Referrer Policy:
   strict-origin-when-cross-origin
2. Here is what I am seeing when I access CC-
   Request URL:
   http://localhost:10039/dx/api/core/v1/dxrest/configuration
   Request Method:
   GET
   Status Code:
   404 Not Found
   Remote Address:
   [::1]:10039
   Referrer Policy:
   strict-origin-when-cross-origin

The readme assumes the local-docker-compose directory has already been created, "Start by cloning this repository locally and cd into the local-docker-compose directory". It's unclear whether this was to be included in the project or something the user should create. I believe updating accordingly would reduce confusion for new users.

Cf196 introduces design studio.

It would be useful to have support for it too in order to easily test.

A mechanism to support containerized releases version will also be useful in order to support multiple versions.

For instance over cf196 is important to support design studio and so on.

Seems there is an error in the load.sh:
sed -i '' ${strSearchAndReplace} ${pathValue}/dx.properties }
I believe that should be
sed -i "${strSearchAndReplace}" ${pathValue}/dx.properties
}`

I also had to run load.sh using
$ bash load.sh /mnt/c/Users/rohir/Downloads/hcl-dx-kubernetes-v95-CF195
since the dash shell fails on the function definition on line 26:
Syntax error: "(" unexpected
I believe both the script and the readme should be updated to use bash instead of sh.

The load.sh script contains this line:
listOfImages+=("DX_DOCKER_IMAGE_PREREQS_CHECKER:hcl-prereqs-checker-image")
This should be:
listOfImages+=("DX_DOCKER_IMAGE_PREREQS_CHECKER:hcl-dx-prereqs-checker-image")

The scripts, when docker compose is executed as the root user, create directories in the .volumes directory. These directories are all created with root:root as the uid:gid. The containers, however run as 1000:1000 (core) and 1000:1001 (dam). These containers can't create directories under ./volumes/core/wp_profile, ./volumes/dam/db or ./volumes/dam/upload. As a result, the container error and exit. It would be good to either create these directories beforehand with the proper uid:gid, or script the init-scripts to do this there.

To fix it, I've added the following lines to set.sh. Just a suggestion:
export DX_PERSISTENT_PATH=/local/DX/data # location of persistent directories

if [ ! -d "$DX_PERSISTENT_PATH/core" ]
then
mkdir -p $DX_PERSISTENT_PATH/{core/wp_profile,dam/{db,upload}}
chown -R 1000:1000 $DX_PERSISTENT_PATH
chown -R 1000:1001 $DX_PERSISTENT_PATH/dam
fi

That also allows for these volumes in the dx.yaml:

• ${DX_PERSISTENT_PATH:?.volumes}/core/wp_profile:/mnt/prereqs-checks-volumes/wp_profile

Personally, I wouldn't want my persistent volume in the same directory where the git scripts are.

Hi

I was running CF212 using docker compose and have my profile persisted using volumes.
Yesterday, I tried to upgrade to CF213 with below steps -

1. Downloaded CF213 container images
2. Loaded images in docker registry using load.sh file
3. Sourced new environment variable using source ./set.sh command.
4. Run the new container using docker compose up command.'

Observed that when wp_profile is upgrading it tries to authenticate with user d3BzYWRtaW4K which was not there in my file based user registry. I have wpsadmin user already in my user registry and was using that only for all the configuration.

The upgrade should have been performed using wpsadmin user rather than d3BzYWRtaW4K. Is this user name hardcoded any where? or is there a way to specify user which should be used during upgrade process?

During the execution of installApps.sh, few exceptions were coming as Websphere_Portal was stopped but not restarted again.
Also, Digital Assests feature is enabled but showing blank page.

Could any one please help me on this issue.