Below is the link I used, which I followed to a tee. I built the image with changed database string, testing the connections, verified Creatio is running, and still the container fails to start???
{ "Logging": { "LogLevel": { "Default": "Debug" } }, "AllowedHosts": "*", "AllowedCorsOrigins": "[\"none.com\"]", "DbProvider": "Postgres", "DatabaseConnectionString": "Server=host.docker.internal;Port=5432;Database=creatio_db;User ID=postgres;password=testpassword123;Timeout=500; CommandTimeout=400;MaxPoolSize=1024;", "X509CertificatePath": "openssl.pfx", "Clients": "[{\"ClientId\":\"IdServiceUsers\",\"ClientName\":\"Bpmonline designer\",\"Secrets\":[\"665b6f638c2da3ecc5d3a1868eb9352f6e01ee4a\"],\"AllowedGrantTypes\":[\"implicit\",\"client_credentials\"],\"RedirectUris\":[\"http://localhost:4200\",\"http://localhost:4200/lib\",\"http://localhost:4200/lib/\"],\"PostLogoutRedirectUris\":[\"http://localhost:4200\"],\"IdentityTokenLifetime\": 300,\"AccessTokenLifetime\": 3600,\"Properties\": {\"AllowedQueryParameters\": \"[\\\"invitationHash\\\",\\\"targetSubject\\\"]\"},\"AllowedScopes\": [\"register_own_resource\", \"get_resource_list\", \"get_client_info\",\"find_clients\",\"remove_client\",\"update_client\", \"add_registrar_client\", \"IdentityServerApi\"]}]", "FeatureManagement": { "Full": true }, "DbConnectionRetryOptions": { "MaxRetryCount": 5, "MaxRetryDelay": 6 }, "IgnoreDbCertificateValidation": true, "MsSqlCompatibilityLevel": 120 }
The Dockerfile: FROM mcr.microsoft.com/dotnet/aspnet:8.0 WORKDIR /app COPY . ./ ENV ASPNETCORE_URLS=http://+:80 EXPOSE 80 ENTRYPOINT ["dotnet", "IdentityService.dll"]
The command I used to run the dotnet8 IdentityService: docker run --env=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin --env=ASPNETCORE_URLS=http://+:80 --env=DOTNET_RUNNING_IN_CONTAINER=true --env=DOTNET_VERSION=8.0.10 --env=ASPNET_VERSION=8.0.10 --workdir=/app -p 80:80 -d creatio-identity-service:latest
Like
Hello,
Please try to set up the Identity Service logging (point 8 from this article) and then run it again to see if any additional details or errors are logged there.
Mira Dmitruk,
I set that up as well after this post and the container fails to start, which returns no logs.
Hello,
If the container fails to start and produces no logs, even after enabling logging as per point 8 in the article, then the issue most likely lies at a runtime or container-level problem, before your application code even runs.
1. Check the Container’s Exit Logs
Run: docker ps -a
Look for the container that exited. Then: docker logs <container_id>
If logs are still empty, it crashed before application output - most likely a .NET runtime issue or entry point failure.
2. Try starting the container manually in interactive mode to see what's wrong:
docker run -it --rm creatio-identity-service:latest /bin/bash
Once inside: dotnet IdentityService.dll
Observe the error. Common issues:
- DLL not found (IdentityService.dll)
- Broken dependencies
- Misnamed or incorrectly copied files
3. Confirm the application runs outside docker. Just to rule out .NET or config issues, run: dotnet IdentityService.dll
in your host machine's CLI, from the same folder you're using in the Docker context. If it fails here, the issue is in appsettings.json or dependencies.
I resolved the issue, thank you for the advice. The issue was caused by a missing openssl file.