xdg-utils | Desktop integration utilities | Dektop Application library

So, I found the problem and document it here if it happens to someone else. It turned out to be how Visual Studio does the building now.

If I right-click and build the Dockerfile in Visual Studio the result will be correct just as my investigations above showed. The problem is that when I wanted to test the image, I run it by F5 (or Ctrl+F5) in VS and in that case Visual Studio does not build my Dockerfile by default. I thought that it used my recently build result (cached), but it actually uses another cached result. For performance reason it builds the project locally and take that result and adds it to the aspnet:3.1-buster-slim image, which means that my custom dependencies are not added.

This behaviour can be controlled by setting in the project file. The default value of if is Fast which does not use my Dockerfile, but setting it to Regular does, on the cost of slower start up. Documentation of this and other settings can be found here: https://docs.microsoft.com/en-us/visualstudio/containers/container-msbuild-properties?view=vs-2019

Cloud functions allows you to deploy only your code. The packaging into a container, with buildpack, is performed automatically for you.

If you have already a container, the best solution is to deploy it on Cloud Run. If your webserver listen on the port 5000, don't forget to override this value during the deployment (use --port parameter).

To plug your PubSub topic to your Cloud Run service, you have 2 solutions

• Either manually, you create a PubSub push subscription to your Cloud Run service
• Or you can use EventArc to plug it to your Cloud Run service

In both cases, you need to take care of the security by using a service account with the role run.invoker on the Cloud Run service that you pass to PubSub push subscription or to EventArc

Old versions of node can't always run the latest npm. npm 7.x only guarantees support for node >= 10.

Remove npm i npm@latest -g to use the package distributed version of npm or install a set version of npm that supports node v9.x. At least fixed to major version (npm i npm@^6) but I prefer to use exact versions so build changes are in your control.

Nodes active LTS releases and list of released node/npm versions.

Gunicorn is an application server for running your python application instance, it is a pure-Python HTTP server for WSGI applications. It allows you to run any Python application concurrently by running multiple Python processes within a single dyno.

Please have a look into the following Tutorial which explains in detail regarding gunicorn.

Regarding Cloud Run, to deploy to Cloud Run, please follow next steps or the Cloud Run Official Documentation:

1) Create a folder

2) In that folder, create a file named main.py and write your Flask code

Example of simple Flask code

There is one possible way.
Create one shell script that is divided into two sections.

• The first section covers all docker pre-requisites required.
• The second section covers the installation command of your custom debian package.

• Host the shell script on an http/https server. Ensure that the client machine where you want the debian package to be installed has access to this http/https server. On your client machine run:
  $ curl -s http://example.com/my_installation_script.sh | bash
• If you want this package installed on a Cloud server, you could host the shell-script inside the Cloud Provider's object storage(AWS: s3, Azure: Blob storage,GCP: Google Cloud Storage) and on you client machine run:
  $ cloud_provider_cli service_name get object_file | cat object_file | bash
• If you are okay with keeping the script public, you could write the script as a gist on Github_gist and host it there for free. On your client machine :
  $ curl -s https://gist.githubusercontent.com/long_url/shell_script.sh | bash You can get the mentioned url by clicking raw option on github to download your shell script from github gist.

Are you running the driver as root? If so try using the --no-sandbox option as the first argument to your driver. Although I would recommend not running it as root because of vulnerabilities.

I have seen from your comment that this solved the issue, but I recommend you create a non root user to run your services if security is really important in your case.

I switched to using a production build for testing by use of a local webserver. I leveraging the [jest-puppeteer][1] library which allows you to start a webserver with your tests.

jest-puppeteer.config.js

The solution comes from the original intent of the docker-compose.yml file which was converted into a kubernetes manifest via a tool called kompose. The original docker-compose file was intended for development and as such had overrides in place to push the local development environment into the running container.

This was because of this in the yml file:

I guess the location where you are filtering branch is wrong. You should filter branches in workflow and not in jobs. Also not worked with orbs, so I'm not sure of the orbs location also.