experience with Docker?

[VJ]

Does anyone have experience with Docker? How do you reboot an image?

I'm trying to make a new image for a small server, based on a Debian image on a Windows server (yes, native linux containers on Windows!).

I pull the Debian image, start a container, run the install script for the small server in the container (*) and commit it as a new image. From this new image I can start a container, but the server does not run. FWIW, it also did not run prior to the commit (at (*)), so I suspect it has to do with starting the service in the container.

The install script should add it such that it is automatically started after a reboot, but I don't know how to reboot an image... Any ideas?

[dZeus]

Does anyone have experience with Docker? How do you reboot an image?

I'm trying to make a new image for a small server, based on a Debian image on a Windows server (yes, native linux containers on Windows!).

I pull the Debian image, start a container, run the install script for the small server in the container (*) and commit it as a new image. From this new image I can start a container, but the server does not run. FWIW, it also did not run prior to the commit (at (*)), so I suspect it has to do with starting the service in the container.

The install script should add it such that it is automatically started after a reboot, but I don't know how to reboot an image... Any ideas?

docker stop <container name/ID> && docker start <container name/ID> ?

Not entirely sure why you would want to restart a container though.. ideally it's a fire&forget, and once you have an updated container you retire the old one and just launch the updated image. All persistent date should be stored outside the container.

[VJ]

Yes, that was what I did... so perhaps my problem is elsewhere... The reason I wanted to restart is that after installation of the software, a reboot is recommended (if you install it on a real system).

It rather seems my problem is in getting the software installed in the container and getting it up and running. It all seems to go fine, the software installs without any errors or warnings, but still I cannot connect to it (the software uses a web-based interface), I've set the ports to access it, but my client never seems to connect to it...

Guess I'll have to try further... Thanks!

[UtwigMU]

Yes, that was what I did... so perhaps my problem is elsewhere... The reason I wanted to restart is that after installation of the software, a reboot is recommended (if you install it on a real system).

It rather seems my problem is in getting the software installed in the container and getting it up and running. It all seems to go fine, the software installs without any errors or warnings, but still I cannot connect to it (the software uses a web-based interface), I've set the ports to access it, but my client never seems to connect to it...

Guess I'll have to try further... Thanks!

can you curl or telnet from the host?

I set up mailcow dockerized and it's working wonderfully for a month now.

[VJ]

That should work... but it is so basic that I have not tried it... I suspect it will go if I open the port, as I start from a Debian pull. For sure something to try.

I was suspecting that I cannot get the installed service from the server to start as I was not sure how to reboot it... but then again a reboot is recommended, not required so it should work even before I try to make it into an image. And it does not... I'll check again if I have all network things correct, as some network modes don't work for linux containers on Windows; the telnet test would be a perfect test for that.

[dZeus]

That should work... but it is so basic that I have not tried it... I suspect it will go if I open the port, as I start from a Debian pull. For sure something to try.

I was suspecting that I cannot get the installed service from the server to start as I was not sure how to reboot it... but then again a reboot is recommended, not required so it should work even before I try to make it into an image. And it does not... I'll check again if I have all network things correct, as some network modes don't work for linux containers on Windows; the telnet test would be a perfect test for that.

Linux containers on Windows? Can you elaborate on that?
Are you saying that you're not running them in a regular Linux VM or through Kubernetes-as-a-service?

[UtwigMU]

I completed my switch to Linux this year. One personal laptop dual boots, everything else is Windows free.

[VJ]

Linux containers on Windows? Can you elaborate on that?
Are you saying that you're not running them in a regular Linux VM or through Kubernetes-as-a-service?

The Windows 2004 update introduced WSL2: https://docs.microsoft.com/en-us/win...s-new-in-wsl-2
In WSL1, docker used a virtual machine in Hyper-V for running linux containers. In WSL2, they can run natively on Windows ( https://docs.docker.com/docker-for-windows/wsl/ ), barring some restrictions.

In the Microsoft App store, you can find different Linuxe flavours (Debian, Ubuntu, ...) which you can install and can assign for use by Docker.

Currently, you cannot run GUI apps in WSL2 (unless you redirect to an X server which can be on your Windows), but Microsoft is working on adding support for that.

(yes, hell froze over )

[dZeus]

What are the limitations with Docker on WSL2, other than GUI? (which is an unlikely but not impossible candidate for Docker containers in the first place)
Afaik, WSL2 runs a native Linux kernel virtualized on top of Hyper-V, unlike WSL1 which didn't use any virtualization at all (and probably completely unrelated to the docker implementation alongside it).

Since you're running with Hyper-V enabled, you may also consider running another Linux VM for a more 'native' container hosting experience if the WSL2 kernel and userland is too limiting.

[VJ]

What are the limitations with Docker on WSL2, other than GUI? (which is an unlikely but not impossible candidate for Docker containers in the first place)
Afaik, WSL2 runs a native Linux kernel virtualized on top of Hyper-V, unlike WSL1 which didn't use any virtualization at all (and probably completely unrelated to the docker implementation alongside it).

Host network mode does not work on Docker for Windows. So perhaps it is not so much a limitation of WSL2, but it is a limitation you have with Linux host on Windows compared to Linux host on Linux.
https://docs.docker.com/network/host/

There are also more restrictions in which devices you can map:
https://docs.docker.com/engine/refer...mmandline/run/

The --device option is only supported on process-isolated Windows containers. This option fails if the container isolation is hyperv or when running Linux Containers on Windows (LCOW).

I don't know if this is fixed in WSL2 though.

Since you're running with Hyper-V enabled, you may also consider running another Linux VM for a more 'native' container hosting experience if the WSL2 kernel and userland is too limiting.

My problem is that the server I want to run is a music server, which can be woken up from the network (not possible if it is a pure VM) and which also prevents the host to go to sleep while music is playing (preventing the VM from sleeping does not prevent the host from sleeping). As it is a linux-only server, I am trying to get it to work in Docker. But I'm very early in learning Docker, so for sure at the moment it is not working because I'm doing something wrong.

[UtwigMU]

You can also get vps from 3 EUR/month on hetzner.

I had major pains with hyperv and Linux networking while teaching a course this week.

[dZeus]

You can also get vps from 3 EUR/month on hetzner.

I had major pains with hyperv and Linux networking while teaching a course this week.

Hyper-V used to prevent the CPU going into deep sleep modes, unlike a Type-2 hypervisor like VirtualBox or VMWare Workstation when not running any VMs.
Not sure if this is still true today, but if it is, I would not recommend using Hyper-V on laptops unless you're intending to run your VMs permanently on, and power usage is comparable with type-2 hypervisors.