ServiceMonitor causes microsoft/iis docker container to exit with error

[robertoandrade]

Containers die with the following log:

Service 'w3svc' has been stopped
APPCMD failed with error code 259
Failed to update IIS configuration

Not sure if this is related at all with #29 and #4 but have been seeing this when running the latest tag of microsoft:iis on a Windows Server 2016 AMI on AWS EC2.

[mcy94w]

Hi @robertoandrade :
Could you please share you Image so I can take a look?

[robertoandrade]

I'm running microsoft/iis:latest no mods.

[mcy94w]

Did you hit this issue recently?

[robertoandrade]

Yes, only starting to mess with containers on Windows, after a few years of Unix. Saw this first yesterday but since I saw similar issues reported against the IIS docker repo and people seemed to always point to it being a ServiceMonitor issue that had been fixed and incorporated into the latest images I thought this could be another one of those, but different since the error code is not the same.

[michha]

Maybe your latest image is an old one. As of today microsoft/iis:latest has an image id of b8f924611ebb (created 3 weeks ago). Try a docker pull microsoft/iis to ensure having the latest version.
I had no problems starting a container from this image.

[robertoandrade]

That's exactly the same I have. A way to repro I guess is setting up an ECS cluster which launches EC2 instances on AWS with their ECS-Optimized AMI (which is preloaded with Docker and both windowsservercore and nanoserver images) and then pull and try to run the container via an ECS task.

When I run it with t2.medium instance types it seems to fail with that code, once I switch over to c5.large or m5.large the problem seems to go away.

[vjgn]

@robertoandrade, I am trying something similar to what you are doing. How did you configure your task in EC2. Look like EC2 has additional dependencies before launching the container. Exposing port 80 definitely conflicts with microsoft/iis image. From AWS docs (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html#windows_task_IAM_roles_bootstrap):

The IAM roles for the task credential provider use port 80 on the container instance, so if you enable IAM roles for tasks on your container instance, your containers cannot use port 80 for the host port in any port mappings

There are additional bootstrap steps that must wired to the container for it launch correctly in AWS ECS. Did you get further in your testing?

[robertoandrade]

Didn't do anything special, was of course exposing port 80 as a different one at the EC2 instance level to avoid that conflict, but interestingly enough, same task definition running on an ECS cluster with a different instance type works just fine, I only see problems when running the cluster with t2.medium/large instance types.

[me-viper]

I have the same issue.
"APPCMD failed with error code 259."
For me problem is reproduced only when containers are handled by AWS ECS. When I start same container on the same EC2 instance manually (aka docker run ...) everything works just fine.

[robertoandrade]

I noticed the same @me-viper but then when I switch the instance types of my ECS cluster to something higher than a t2 it ECS launches the container just fine without errors.

[lugoues]

I see the same thing as @me-viper, and it is inconsistent. The container will fail to launch repeatedly for a time (sometime hours), and then start working.

I'm already running m5.large and m5.xlarge instances, so it may not be related?

I grabbed all the event logs from a dead container and nothing seemed out of the ordinary, I can provide them if that would help.

[mebyz]

i'm experiencing the same issue on our aws ECS infrastructure

here are the steps we followed :

1. create an aws ecs windows cluster (m5.large)
2. create a task definition linked to our asp .Net app (a docker image stored on dockerhub)

when the task starts, here is what we see in the log (cloudwatch) :

"
Service 'w3svc' has been stopped
APPCMD failed with error code 259
Failed to update IIS configuration
"

then, the tasks stops (obviously)

just to be sure the issue is not related to our app specifically, we also tried switching our task definition to this public dockerhub image : microsoft/aspnet

but the issue is the same, and the logs are showing the same error(s)