search

dockur / windows

Windows inside a Docker container.
MIT License
15.51k stars 1.27k forks source link

Unable to self-restart. #591

Closed Cuphead74832 closed 1 week ago

Cuphead74832 commented 3 weeks ago

Operating system

Ubuntu 24 (Latest)

Description

I use the solution given in here: https://github.com/dockur/windows/issues/572 my container shutsdown, docker container restarts.

Expected result:

Docker compose

services: windows: image: dockurr/windows container_name: windows environment: VERSION: "win11" DISK_SIZE: "60G" MANUAL: "Y" devices:

Docker log

Unable to access them :( but the problem also happens in an older machine i have so it will be easy to re-create. Just use the compose file and then trigger a shutdown once in the OS. To fasten the process you can just change "win11" to an ubuntu installer or something and once it boots just shutdown so you dont have to wait for install as cancelling the install on the windows installer results in a reboot hopefully someone else can get actual logs.

Screenshots (optional)

No response

kroese commented 3 weeks ago

I have no idea what you mean by these loops. Without seeing your logfile its impossible for me to understand what you are doing and what is happening.

They may contain important error messages or the reason for the reboots.

So what is the reason you cannot view the output of the container?

Cuphead74832 commented 2 weeks ago

Cuphead@ubuntu24: docker logs windows ` Cuphead@ubuntu24:`

That or i typed it wrong. Attempted to load the ISO locally resulted in a never ending HTTP error unable to access stuff.

kroese commented 2 weeks ago

Then use the docker run command example from the readme, and you will see all the lines.

You are much too vague to be helped now, what "HTTP error"? What does it say exactly?

Cuphead74832 commented 2 weeks ago

Error 500 for external connections. Connection Refused for internal connections.

kroese commented 2 weeks ago

What is the output of the docker run command from the readme? Just run it and make screenshots of everything you see.

Cuphead74832 commented 1 week ago

Sorry for the inconvenience, i recently had a docker update failure and in the last week of inactivity i been recovering important containers. I am still doing that but will do "docker run" sometime during my free time. Will re-open when back and running.