ssh-server | docker image of an SSH server | SSH library

I am trying to connect to openssh-server in docker container using ssh:

I am trying to deploy a spring boot docker container on OpenJDK image into APP service on Azure. What baffles me is the time the web app takes on initial run (only during the initial run). I also see on the KUDU console that the container started up in less than 6 seconds but the APP service ran for more than 200 seconds and fails. Please see the attached screenshot. Has some one faced this issue before?

Edit 1: Adding the Docker File

Working with Ubuntu 20.04, Packer and vSphere, I am having issues getting the autoinstall to work correctly. It will load and enter the autoinstall command in the boot options section, and when it processes I see it determine the network but afterwards it boots like a normal install and prompts for user interaction.

I have verified that I can reach the User-Data file from the browser and it exists, and that it is correctly typing in the command as I watch it in the vSphere view.

Questions:

1. is the boot command correct? (I have tried a variety of options after some time googling all the same results)
2. Is there a parameter I am missing to override the GUI?

Boot Command:

I'm using dockerfile to create an Image And I want every time when the docker container starts the ssh connection should also start and then the ngrok should also start but I'm not able to use CMD command can you guys please help me with it.

I'm using Laravel Sail and have published the Dockerfile (so I can edit it manually). The reason being that I need to use an OpenSSH server on the container itself for a program I'm using.

I am able to install OpenSSH by adding && apt-get install -y openssh-server to the packages section and configure it with the following:

I have to run the python program in Redhat8. So I pull Redhat docker image and write a Dockerfile which is in the following:

I install wsl on windows 10 and install Ubuntu 20.04 LTS and open linux terminal and run this commands : sudo apt update sudo apt upgrade sudo apt dist-upgrade sudo apt install joe wget p7zip-full curl openssh-server build-essential zlib1g-dev libcurl4-gnutls-dev libncurses5 sudo apt-get install zlib1g-dev

then i Unpack the LinuxPAServer22.0.tar.gz and run it and Creating a Connection Profile in delphi and Adding the Installed SDK to Delphi.

i create consol application in Delphi Delphi in "Linking" show 138 error :

I'm using Visual Studio to connect to a docker container via SSH for remote development using CMake as the build system. When Visual Studio launches the project for the first time or a CMakeLists.txt file has been altered, Visual Studio configures, allowing me to view, compile and run the CMake targets, and other CMake settings also become available in the UI (such as settings from the 'Project' drop down), however, when reopening the project, Visual Studio does not seem to detect the CMake Project or reconfigure automatically, meaning no targets are shown hence not possible to compile, or if shown don't work, and no settings for CMake are shown in the UI; I could theoretically update a CMakeLists.txt file which after relaunching again could cause a regenerate, causing Visual Studio to detect the project, show the targets and general settings relating to CMake in the UI, but this is not ideal and could cause the entire project to require recompiling.

Steps to reproduce:

1. Create C++ CMake Project in Visual Studio 2022
2. Run Docker container and add SSH connection info in Visual Studio options
3. Replace the default 'x64-Debug' in CMakeSettings.json with 'Linux-GCC-Debug'
4. Wait for automatic CMake generation or press Generate on the popup "C++ IntelliSense information may be out of date, generate the CMake cache to refresh.."
5. Everything works perfectly now; the "Select Startup Item" menu button should be available to select, compile and execute the target/s specified from the CMakeLists.txt files. Other CMake buttons should now be available, (e.g. Project -> Configure Cache)
6. Quit Visual Studio
7. Open the project again in Visual Studio
8. There does not appear to be a way to restore the working state, Visual Studio does not know the CMake targets anymore, we can no longer compile the project, nor run it. There appears no way to cause Visual Studio to reconfigure within the UI. The existing targets may appear, but no longer work.

I have then followed the tutorial for remote cache: https://devblogs.microsoft.com/cppblog/open-existing-cmake-caches-in-visual-studio/

Doing the steps:

1. Replace configuration 'Linux-GCC-Debug' with 'Existing Cache (Remote)'
2. Update cacheRoot to the path that contains CMakeCache.txt on the remote system

The regenerate popup shows ( "C++ IntelliSense information may be out of date, generate the CMake cache to refresh.." ), pressing regenerate works the first time, but then subsequent re openings of the project result in nothing happening again. No targets / executables to choose.

This issue does not occur for local MSVC CMake projects, the available targets are always shown immediately upon relaunch, along with all other Project settings being available in the UI.

Is this a bug in Visual Studio, or, is there something I'm missing so that Visual Studio always uses the existing cache to configure itself to make the targets available for compiling and executing, whenever I launch the existing project? How do IDE's typically detect CMake targets, perhaps knowing this could give a hint on solving the issue.

Visual Studio Version: 17.0.5

Docker File:

I have a Dockerized Django application, which I'm orchestrating with Supervisor, which is not optimal but needed when hosting on Azure app services as their multi-app support with docker-compose is still in preview mode (aka. beta).

According to best-practises I have configured each application within supervisord to emit the logs to STDOUT. It works fine when I create the Docker image locally, run it and check the docker logs. However, when I have deployed it to Azure app services and check the logs, my web-application (Gunicorn) is logging as expected, however, the logs from NGINX don't appear at all.

I have tried different configurations in my Dockerfile for linking the log files generated by NGINX (linking to both /dev/stdout and /dev/fd/1 for example) and I have also gone into the the nginx.conf config and trying to log out directly to /dev/stdout. But whatever I do it work fine locally, but on Azure the logs don't show any NGINX-logs. I've pasted relevant configuration files, where you can see the commented lines with the options I've tried with. Hope someone can help me figure this one out.

EDIT: I've also tried logging the NGINX app to a log-file in the system, which also works fine locally, but not in Azure app-services. I tried deactivating the "user nginx" part in nginx.conf as I though it could have something to do with permissions, but that didn't help either.

EDIT 2: I also tried creating the log files in my home-directory in the web-app at Azure, thinking it may had to do with not being able to create logs in other directories - again, it works locally, but the logs in Azure are empty.

Dockerfile