Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to build image from latest 2019-Datacenter-Core #5332

Open
Trojan295 opened this issue Nov 26, 2024 · 0 comments
Open

Failed to build image from latest 2019-Datacenter-Core #5332

Trojan295 opened this issue Nov 26, 2024 · 0 comments

Comments

@Trojan295
Copy link

What happened:

I'm trying to build an image for AKS from the image SKU 2019-Datacenter-Core. It fails for image version 17763.6414.241004 or later with the following error:

    azure-arm: Start-Service : Service 'OpenSSH SSH Server (sshd)' cannot be started due to the following error: Cannot start service
    azure-arm: sshd on computer '.'.
    azure-arm: At C:\Windows\Temp\script-6745f9f6-4784-99a2-8a03-0793c3a69f24.ps1:400 char:5
    azure-arm: +     Start-Service sshd
    azure-arm: +     ~~~~~~~~~~~~~~~~~~
    azure-arm:     + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
    azure-arm:    ServiceCommandException
    azure-arm:     + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

The last working image version is 17763.6293.240905.

What you expected to happen:

Image build completes successfully.

How to reproduce it:

Build an image with the following source image:

    "windows_image_sku": "2019-Datacenter-Core",
    "windows_image_version": "17763.6532.241101",
    "windows_image_publisher":"MicrosoftWindowsServer",
    "windows_image_offer":"WindowsServer",

Anything else we need to know?:

I found this thread, where people reported, that there is some permission problem on the ssh logs directory.
https://serverfault.com/questions/1166382/openssh-ssh-server-wont-start-on-windows-server-2019-after-windows-updates

In my case the logs directory does not exist, by the time, when Start-Service sshd is executed.

Environment:

  • AgentBaker version: dev
  • Kubernetes version (use kubectl version):
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
    Packer: v1.11.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant