node-app | Runtime Evironment library

As @Sysix pointed out, docker will always overwrite the folder in the container with the one on the host (no matter if it already existed or not). Only those files will be in that folder/volume that were created either on the host, or in the container during runtime.

Learn more about bind mounts and volumes here.

Record Audio and Video with MediaRecorder

I solved the problem using MediaRecorder. Using MediaRecorder API, you can start and stop the recorder, and collect the stream data as they arrive.

The MediaStream can be from:

• A getUserMedia() call.
• The receiving end of a WebRTC call.
• A screen recording.

It support the following MIME types:

• audio/webm
• video/webm
• video/webm;codecs=vp8
• video/webm;codecs=vp9

The following demo demonstrates that and the code is available as well

I still have to solve the second concern!! Any idea for mapping the local and remote video frames?

You need to add startup command, you can try it.

This is a community wiki answer. Feel free to expand it.

As already mentioned by @TomerLeibovich the main issue here was due to the Probes Configuration:

Probes have a number of fields that you can use to more precisely control the behavior of liveness and readiness checks:

• initialDelaySeconds: Number of seconds after the container has started before liveness or readiness probes are initiated. Defaults to 0 seconds. Minimum value is 0.

• periodSeconds: How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.

• timeoutSeconds: Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1.

• successThreshold: Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup Probes. Minimum value is 1.

• failureThreshold: When a probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready. Defaults to 3. Minimum value is 1.

Plus the proper Pod eviction configuration:

The kubelet needs to preserve node stability when available compute resources are low. This is especially important when dealing with incompressible compute resources, such as memory or disk space. If such resources are exhausted, nodes become unstable.

Changing the threshold to 1 instead of 3 and reducing the pod-eviction solved the issue as the Pod is now being evicted sooner.

EDIT:

The other possible solution in this scenario is to label other nodes with the app backend to make sure that each backend/pod was deployed on different nodes. In your current situation one pod deployed on the node was removed from the endpoint and the application became unresponsive.

Also, the workaround for triggering pod eviction from the unhealthy node is to add tolerations to

I suspect that your problem is in here:

Alpine uses musl for its C library. You can either use a different non-alpine based image such as node:12-buster-slim or any of the other non-Alpine tags here, or try to get it to work by setting up glibc with the instructions here. Using a Debian or Ubuntu based image would be the easiest way forward.

Currently, virtual application is not supported for Linux environment on Azure.

Here is some supported links:

1. Virtual directory is IIS concept basically. we can't create virtual directory for Linux.
2. For Windows apps, you can customize the IIS handler mappings and virtual applications and directories.
3. Just like Joey Cai said, you could use container to proxy multiple applications on Linux, but virtual application is unreachable, because the port would be occupied for the default application.
4. Running multiple sites in a single Linux web app was not officially supported.

From AWS docs and what you've posted the likely reason is that you are missing /bin/bash in your docker_run.sh:

User data shell scripts must start with the #! characters and the path to the interpreter you want to read the script (commonly /bin/bash).

Thus your docker_run.sh should be:

I suspect this issue is due to the caller not having permissions to the repository, I recommend you to check the account you are using to run this command has the required permissions to interact with Source Repositories.

If missing, I would suggest adding the role roles/source.admin to your account, using these instructions, and then try to run the command again.