Omnis App Server running in Windows Docker Container

[Alan Davey]

Hi Alain and Wayne,

Thanks.   I'll double check the port and printer when I'm back online.   I
didn't need to do anything with those when running the container on my VM
running 2019 server.  But there is clearly some difference between running
it on windows 10 Enterprise edition and 2019 server.

Regards,

Alan

On Wed, Nov 23, 2022, 10:39 AM Wayne Germann <wgermann at pacific.edu> wrote:

> Do you have a Defualt Printer assigned to the Windows Server Container?
>  Omnis crashes with no default printer.
>
> -----Original Message-----
> From: omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> On Behalf Of
> Alain Stouder Omnis
> Sent: Wednesday, November 23, 2022 5:38 AM
> To: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
> Subject: Re: Omnis App Server running in Windows Docker Container
>
> CAUTION: This email originated from outside of Pacific. Do not click any
> links or open attachments if this is unsolicited email.
>
> Hello Alan,
>
> Don’t know much about docker but if you install a web server you must tell
> the windows firewall to open pour 5912.
>
> HTH,
> Alain
>
> > On 22 Nov 2022, at 22:41, Alan Davey <david.a.davey at gmail.com> wrote:
> >
> > Hi $all,
> >
> >
> >
> > I’m trying to create a windows container (Server 2019) with IIS and
> > Omnis App Server and test on my Windows 10 development environment.
> > I’ve created the container, but for some reason the OMNISServerx64
> > service refuses to start.  IIS is running fine and I’m able to connect
> > to it and see my web pages.  I’m just curious if anyone has been
> > successful in getting this type of container working on windows 10.
> >
> >
> >
> > My Dockerfile:
> >
> > FROM
> > mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019
> >
> >
> >
> > RUN powershell -NoProfile -Command Remove-Item -Recurse
> > C:\inetpub\wwwroot\*
> >
> >
> >
> > WORKDIR /inetpub/wwwroot
> >
> > COPY content/ .
> >
> >
> >
> > RUN mkdir c:\Studio
> >
> > WORKDIR /Studio
> >
> > COPY Studio/ .
> >
> >
> >
> > RUN cmd /c Omnis-App-Server-10.22-x64.exe --mode unattended
> > --installscope allusers --serialno "XXX XXX XXX" --serverport 5912
> >
> >
> >
> > RUN cmd /c net start OMNISServerx64
> >
> >
> >
> > After building the container and running it, I then shell into the
> > container to check the Omnis service, but it is not running.  When I
> > execute the service manually, I get:
> >
> > C:\Studio>net start OMNISServerx64
> >
> > The OMNIS Server x64 service is starting.
> >
> > The OMNIS Server x64 service could not be started.
> >
> >
> >
> > The service did not report an error.
> >
> >
> >
> > More help is available by typing NET HELPMSG 3534.
> >
> >
> >
> > Unfortunately there are no error messages or logs that point to what
> > the problem is.
> >
> >
> >
> > As a workaround I can spin up a virtualbox with Windows Server 2019
> > running, build the container and then see that the service is running
> > fine.  So I know everything in the docker file is fine.  It just seems
> > that something is missing from my Windows 10 environment.
> >
> >
> >
> > Any thoughts on how to resolve this would be greatly appreciated.
> >
> >
> >
> > Thanks,
> >
> >
> > Alan
> > _____________________________________________________________
> > Manage your list subscriptions at https://lists.omnis-dev.com Start a
> > new message -> mailto:omnisdev-en at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com Start a new
> message -> mailto:omnisdev-en at lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>