Skip to main content

Docker network configuration format

Formatting docker network inspect output

I use to fight against the "--format" value of "docker network inspect" in order to get what I want.

One of the things often need is the "Subnet" and "Gateway", so I keep it here for the archives:

$ docker network inspect worpdress-network --format "{{(index .IPAM.Config 0).Gateway}}"

And also:

$ docker network inspect worpdress-network --format "{{(index .IPAM.Config 0).Subnet}} {{(index .IPAM.Config 0).Gateway}}"

But if I want to loop on the networks:

$ docker network list --format "{{.Name}}"
  bridge
  host
  neo4j-core-01-network
  neo4j-core-02-network
  neo4j-core-03-network
  none
  worpdress-network

That helps me to have my kind of "list of named network"

$ for N in $(sudo docker network list --format "{{.Name}}"); 
    do 
      sudo docker network inspect ${N} --format "{{.Name}} {{(index .IPAM.Config 0).Subnet}} {{(index .IPAM.Config 0).Gateway}}" 2>/dev/null ; 
    done

Giving:

bridge 172.17.0.0/16 

neo4j-core-01-network 172.18.0.0/29 172.18.0.1
neo4j-core-02-network 172.18.0.8/29 172.18.0.9
neo4j-core-03-network 172.18.0.16/29 172.18.0.17

worpdress-network 172.19.0.0/16 172.19.0.1

Note: blank lines are due to the "host" and "none" network, whch are dummy networks, without IP address assigned to them

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "