Docker Image Available

We’ve released a preview docker image if you’d like to just pull and get running with PSU. It’s currently running the 1.2.1 nightly build.

https://hub.docker.com/r/ironmansoftware/universal

4 Likes

When will this image be updated with new versions?
I see that 1.2.2 i9s the newest :slight_smile:

We are working on getting nightly builds released as preview but were not there yet. I can publish another preview today. That said, not much has changed since 1.2.2

Would we see a Docker image built on top of Windows Server Nano or Core? I’m interested to use Docker, but I do also need the Active Directory module that currently cannot run just PWSH

I don’t see why not. We are basing our image off the PowerShell and they have Nano server and core images. I’ll add it to our backlog.

1 Like

I have been trying to get the docker image to run properly, but I’m encountering lots of errors.
I am using the latest image and experience this.

  1. Dashboards do not launch, even with just the example content provided. WHen going to view link it displays a red triangle with exclamation mark and says “one or more errors encountered”
  2. Adding api’s do not work, it just results in a 404

I have checked the container log and there the following log messages appear,

Grpc.Core.RpcException: Status(StatusCode=Unavailable, Detail=“failed to connect to all addresses”),
at Universal.Server.Services.DashboardProxy.GetDashboard() in C:\src\universal\src\Universal.Server\Services\DashboardProxy.cs:line 204,
Failed to get dashboard

THis is refering to a windows path? this seems strange to me, shouldn’t this point to linux style paths ? Maybe a reference to a file that is not there?

The path is due to the builder. It’s referencing the original source files.

That said, I’m seeing this as well. I’ll look into it today.

We had an issue with PSU that was causing APIs\Dashboards to exit prematurely and that’s what is causing this. I’ll be releasing the 1.2.3 version tomorrow and it will include a new container image with this fix.

Note that the new docker image resolves this issue.