iproute2 | iproute2 with support for new Qdiscs | Networking library

I'm buildinga a docker image using a Dockerfile to build it. I have put ARG DEBIAN_FRONTEND=noninteractive in the beginning of the Dockerfile to avoid debconf warnings while building.

The warnings does not show up when using apt-get install inside the Dockerfile. However when executing a sh script (install_dependencies.sh) from the Dockerfile that contains apt-get install commands, the warnings show up again. I also tried to set DEBIAN_FRONTEND=noninteractive inside the sh script itself.

I can solve this by adding echo 'debconf debconf/frontend select Noninteractive' | sudo debconf-set-selections in the sh script before the apt-get install commands but I would want to avoid that, since any fail in the script would leave debconf select to Noninteractive.

Dockerfile:

The following webpage contains all the source code URLs for the LFS project:

https://linuxfromscratch.org/lfs/view/systemd/chapter03/packages.html

I've wriiten some python3 code to retrieve all these URLs from that page:

I have a project which has a docker-compose file and a Dockerfile. The project is open here GitHub

I'm building a demo project with:

• Traefik
• Snort 3
• A NodeJS API dummy for testing

The issue is that in my Docker file I have a command like this to run on Snort

I want to create a virtual private network in which I can manage virtual machines's interfaces with iproute2.

For example, with AZ CLI, I create two virtual machines in subnet 172.16.1.0/24, each machine has one interface: az network vnet create -g test -n net --address-prefix 172.16.0.0/16 --ddos-protection false --vm-protection false

az network vnet subnet create -g test --vnet-name net -n subnet1 --address-prefixes 172.16.1.0/24 --network-security-group test

az network nic create -g test -n vm1-nic --vnet-name net --subnet subnet1 --private-ip-address 172.16.1.10 --public-ip-address vm1-pub

az network nic create -g test -n vm2-nic --vnet-name net --subnet subnet1 --private-ip-address 172.16.1.11 --public-ip-address vm2-pub

az vm create -g test -n vm1 --image rhel --size Standard_F4 --generate-ssh-keys --nics vm1-nic

az vm create -g test -n vm2 --image rhel --size Standard_F4 --generate-ssh-keys --nics vm2-nic

Then I connect on vm1 with ssh, ping 172.16.1.11 should work.

It is possible to change vm's network interfaces ip addresses with iproute2 command? Like I put 10.100.0.1/24 on vm1's interface and 10.100.0.2/24 on vm2's interface with iprout2 command and I ping to 10.100.0.2 from 10.100.0.1.

I want to understand how virtual machines are connected, the connection is simulated as a wired connection which we can configure network interfaces?

Where is the sub command "depends" of "apt" documented, especially its output format and the meaning of the pipe symbol in the output?

"man apt" doesn't mention this sub command at all.

Example invocation:

I have three Azure Pipeline agents built on Ubuntu 18.04 images and deployed to a Kubernetes cluster. Agents are running the latest version, 2.182.1, but this problem also happened using 2.181.0.

Executing build pipelines individually works just fine. Build completes successfully every time. But whenever a second pipeline starts while another pipeline is already running, it fails - every time - on the "Checkout" job with the following error:

The working folder U:\azp\agent\_work\1\s is already in use by the workspace ws_1_34;Project Collection Build Service (myaccount) on computer linux-agent-deployment-78bfb76d.

These are three separate and distinct agents running as separate containers. Why would a job from one container be impacting a job running on a different container? Concurrent builds work all day long on my non-container Windows servers.

The container agents are deployed as a standard Kubernetes "deployment" object:

I want to parse output of popen(3), but it looks like I have to repeat popen() call.

I am using a VSCode devcontainer to write a Java application. I put it down for about a month, came back to work on it and now I'm getting some unfamiliar errors.

Here I'll provide my relevant configuration files for my devcontainer environment.

My Dockerfile is as below:

I have a docker container that has a healthcheck running every 1 min. I read that appending "|| kill 1" to the healthcheck in dockerfile can stop the container after healthcheck fails, but it does not seem to be working for me and I cannot find an example that works.

Does anybody know how I can stop the container after marked as unhealthy? I currently have this in my dockerfile: