linux-doc | Linux Documentation 中文翻译计划

I started to work with GitLab CI/CD. I have setup my own GitLab-runner with docker executor. It is working fine. When I read about docker, I came to know that it creates a separate space for each run so that we could even access it and use it. I would like to know the path in which the docker images are created.

This is my config.toml

I'm learning more about Azure, Containers, App Services and the VNet integration (preview).

I can successfully deploy my dotnet core (3.1) API directly to an Azure App Service (Linux flavor) and set up the appropriate VNet integration, which allows the API to access an on-prem 192.168.. address while the API is publicly accessible.

What I would like to do is deploy the code as a Docker image to the Azure Container Registry and then deploy the container image to an App Service and use the same VNet integration.

When I do this the containerized version of the App Service does not reach the same 192.168.. address that the direct-to-app service does.

Azure informs me that more information on this issue can be found here: https://github.com/Azure/app-service-linux-docs/blob/master/app_service_linux_vnet_integration.md

Direct from that link:

Linux App Service VNet Integration Azure Virtual Network (VNet) integration for Linux Web App is currently in Preview. Customers can use the VNet feature for development and integration testing with your web apps. Please do not use the feature for production purposes. Learn about how to configure VNet with your web app.

During Preview you will need to modify your application in order to integrate with VNet. This is a temporary limitation during VNet Preview release, we will remove the limitation before GA. In your application, please use the PORT environment variable as the main web server’s listening port, instead of using a hardcoded port number. The PORT environment variable is automatically set by App Service platform at startup time. For example, for a Node.js Express app, you should have the following code as part of your server.js file. The full example can be found on Github.

app.listen(process.env.PORT);

ASPNETCORE_URLS is the recommended way to configure ASP.NET Core docker image and here is the DockerFile example.

Note: we’re making continuous improvement to this VNet integration Preview feature for Linux web app, we will roll out feature improvements in the next few months.

In short I have to apply a small workaround while VNet is in preview.

The page provides a link to a DockerFile that can apparently be used for dotnet core apps. https://github.com/dotnet/dotnet-docker/blob/7c18c117d9bd2d35e30cdb4a1548ac14b9f0f037/3.0/aspnetcore-runtime/nanoserver-1809/amd64/Dockerfile

If i take a copy of that DockerFile my app no longer compiles with errors around the escape character. If i remove those i then receive other error messages where many of the commands are not known.

My problem is I do not fully understand how to make this work.

What Do i have to include in my apps DockerFile (My verison is below) to make sure that the containerized version of the app is correctly set up to use this workaround?

My current DockerFile (default docker file for the API in Visual Studio). The only thing I changed here was the version of Windows that was being targeted.

I discover programming with vectorized data types for SIMD instructions (with this tutorial). From what I understand, a vector has a fixed size of 16 bytes. This schematic details it well and seems to answer my question:

A set of instructions including the basic operations (but also some more specific ones) is provided.

Nevertheless, just out of curiosity, I would like to know if there was a way to vectorize "custom data", and by that I mean mostly structures. I suppose that if the size of the structure is within the 16 byte range, it is possible, because in the end, the types are only byte sizes, however the instruction set does not seem to allow to operate directly on structures, for example to get a field.

So my question is the following: are we limited to the simple standard C types when vectorizing and SIMD operations? If not, how do we proceed? If yes, are there parallelization methods (other than multithreading) to operate simultaneously on structure vectors / arrays?

I have a Java application that runs in docker based on the cutdown alpine distribution, I want umask to be set to 0000 so that all files created by the application in the configured volume /music are accessible to all users.

The last thing the Dockerfile does is run a script that starts the application

I am using Azure CLI 2.0 on a windows machine and I am trying to create a Docker VM using this Microsoft documentation:

A common setup with Docker: Two linux containers, one a .NET Core WebServer using EntityFramework Core 2.2.6, the other a MS-SQLServer 2017. Persistent data is being held in a Docker volume. Using docker-compose, it's not a swarm.

When starting the SQLServer container, one must provide the SA password as an environment variable to the container. However you provide that, it is possible to later read this env from outside the container using docker container inspect. Which obviously compromises security.

That leads me to two questions:

1. (discussed in another thread) What better ways are there to provide the SA password to the SQLServer?

2. The Microsoft help states that it's best to change the SA password directly after starting the container. When I do that in my WebServer code, EntityFramework is already connected with the default SA password (the one I provided as env). I can change the password easily. But how can I tell EntityFramework to reset it's ConnectionString?

Here is my code so far:

The goal is to get the version of a source package in a reprepro-based deb repository.

Since the tracking of source packages is still experimental in reprepro, the list command has issues with --list-format option and thus cannot be used in this use case.

An excerpt of the output of the command to print out all information about tracked source packages is:

We are building a application using Dotnet 2.0 and Docker. We are running the containers in Linux mode. This works well on our local Windows 10 machines with Docker for Windows, and on AWS ECS. Now we are trying to add a CI pipeline to deploy to AWS ECS.

We set this server up using a AWS windows 2016 AMI running on EC2, but we quickly learned that we cannot use Docker for Windows. We can use the AWS Windows with Containers AMI with docker installed, but this does not support Linux containers.

Is there something we can do to get the machine to support Linux containers? We don't actually have to run Linux containers on the machine, we are just using it to build images, upload them to ECR and use ECS-CLI to run containers. Do we just need to move our build server to a linux AMI to support this (most of the team is lighter on Linux knowlege and a GUI is nice on a build/tools server)

Any thoughts? We are using Jenkins as our CI tool. I have seen the hack to get Linux containers running here but I don't want to use a hack on a important server in our development process.

I am trying to create a docker image based on the Kali Linux base image, and I need to install NodeJS as a dependency for my application.

Here's my Dockerfile: