Kubernetes is deprecating Docker as a container runtime after v1.20, so now there is more and more servers, using other container runtimes (containerd, CRI-O) instead of Docker.
But Visual Studio Code Remote - Containers extension doesn't see containers, that using runtime other than Docker.
Is it possible to add support for other container runtimes to VS Code Remote Containers extension?
Related
I'm trying to build a robot which is run on my local system but acts upon the Remote Desktop through UiPath's Native RDP support. I've installed the Microsoft Remote Desktop Apps extension on my local system, and the Remote Runtime in my desitnation remote machine.
When I had used the Remote Desktop Connection application to connect to the remote and machine and work with Uipath, every selector worked with just minor modifications.
Now I've had to switch over to use Microsoft Remote Desktop app to connect to Remote machine and use the same. However, Uipath is not able to recognize any sort of selector inside the remote machine now.
What could be the reason for this? It works perfectly fine with Windows' built in Remote Desktop Connection, but not with Microsoft Remote Desktop. Any solution can be worked around for this?
I am working on being able to connect services hosted within a Windows container to SQL Server using Integrated Security.
As per the Microsoft documentation, I have created a grouped managed service account (gMSA), credentials spec and my container hosts have access to the gMSA - https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/manage-serviceaccounts
I have been testing the connection by using the SQL Server PowerShell module within the following container:
docker run --security-opt "credentialspec=file://mygsma.json" -it mcr.microsoft.com/windows/servercore:ltsc2019 powershell
Problem:
When running the container in hyper-v isolation mode, I get the following error SQL Server error:
Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
If I run the container in process isolation mode, I am able to successfully login to SQL Server using the gMSA. As far as I'm aware there is nothing to suggest that Integrated authentication for hyper-v containers is not supported.
There was a bug which prevented you using gMSAs with Hyper-V isolated containers on Windows 10 versions 1703, 1709, and 1803. However, I'm using Windows 10 version 1809 and can confirm the gMSA can be accessed by the container.
Any ideas?
I have a solution consisting of different small web-services, which right now I can simply build and run each in their own container via docker-compose.
Now, another service will be added, which will need some data access. Since running a mssql server on in a docker container is rather easy and basically consists of one entry in the docker compose, I would like to do the following:
Create a SQL Database project and add it to my solution
Configure the database project, so that it fits the need of the web service
build a containerized SQL-Sever and automatically publish the database schema from my database project
build the web service and connect it up with the containerized SQL server
The goal is, that after running docker-compose, everything should be up and running.
Is this possible as described?
One additional note: The whole thing is just a hobby project, I want to get familiar with docker, APIs and access to databases.
I have web application which uses angular 6 on client side,asp .net core on backend and sql server as a database.
I want to deploy this web apllication on nginx server using docker.
I have installed docker on windows and created nginx container also,but I dont know how to map host application to container and how to serve application.
Note : operating system is windows.
Use Docker-compose (https://docs.docker.com/compose/). You can connect your containers via extra_hosts and start your app with one command
How can you query a Pervasive v13 database from an application that's running inside a docker container?
It would seem you'd have to install the pervasive sql client inside the docker container to accomplish this, but I cannot locate any documentation regarding this task.
Please advise.
Yes, you would need to install the Pervasive v13 client within the Docker container. You'd need to use the client for the OS of the container. If the container is Linux based, use the Linux client. If it's Windows, use the Windows client.