phusion-baseimage seems incapable, out-of-the-box, of resolving hostnames

This issue has been driving me nuts for weeks in my own network, so I tried, and unfortunately successfully reproduced this same issue on a digital ocean 'droplet', whatever those are.
The phusion-baseimage seems incapable, out-of-the-box, of resolving, at least this one critical domain name.  Any guidance?
-- Hugh
root@debian-2gb-nyc3-01:~/lib/docker/puppet# IMAGE="puppet-agent:0.9.19" && /usr/bin/docker build --rm=true --tag="$IMAGE" .

Step 11/20 : CMD /sbin/my_init
 ---> Using cache
 ---> 2ea3e555194a
Step 12/20 : RUN apt-get update && apt-get upgrade -y -o Dpkg::Options::="--force-confold"
 ---> Running in 7348cdbb228e
Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
^C

root@debian-2gb-nyc3-01:~/lib/docker/puppet# host archive.ubuntu.com
archive.ubuntu.com has address <IP_ADDRESS>
archive.ubuntu.com has address <IP_ADDRESS>
archive.ubuntu.com has address <IP_ADDRESS>
archive.ubuntu.com has address <IP_ADDRESS>
archive.ubuntu.com has IPv6 address 2001:67c:1360:8001::17
archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::11
archive.ubuntu.com has IPv6 address 2001:67c:1360:8001::21
archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::14

root@debian-2gb-nyc3-01:~/lib/docker/puppet# iptables -S -t nat
-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P OUTPUT ACCEPT
-P POSTROUTING ACCEPT
-N DOCKER
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT ! -d <IP_ADDRESS>/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -s <IP_ADDRESS>/16 ! -o docker0 -j MASQUERADE
-A DOCKER -i docker0 -j RETURN

I'll have to look into it; in the meantime, if anyone else is able to shed any light on this, that would be great.

@hyperknot any ideas?

We had a very similar ticket a while ago. The solution was that it was a Docker host configuration issue, which got solved by changing something on the host.

Yes, that may have been me.  I am using all the tricks listed at:
https://github.com/phusion/baseimage-docker/issues/357.
But I took this out of my cluster and onto digital ocean and was able to reproduce the issue.  I have DNS set to <IP_ADDRESS>, etc., and I can resolve the missing domain from the host, but cannot do so from inside the container.  Neither will my docker build an image fully work, because these name resolution issues frustrate my attempts to use apt-get in my Dockerfile.
Any further thoughts on how I might get this to work?
-- Hugh
To reproduce this issue, I am running this lib/setup_do_droplet.sh script:
#!/bin/bash
set -x

target_ip="$1"
target="root@${target_ip}"
remote_path='/root/docker-helper-scripts/lib'
puppet_container_bootstrap='/root/docker-helper-scripts/lib/docker/puppet'
bootstrap_script='/root/docker-helper-scripts/lib/sh/bootstrap_docker.sh'

/root/docker-helper-scripts/lib/sh/iptables_starter.sh -u 2>&1 > /dev/null
ssh $target "apt-get update"
ssh $target "apt-get upgrade"
ssh $target "apt-get install rsync"
ssh $target "ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa"
ssh $target "mkdir -p $remote_path/{sh,docker}"
scp $bootstrap_script "${target}:${remote_path}/sh/"
/usr/bin/rsync -avz "$puppet_container_bootstrap" "${target}:${remote_path}/docker/"
ssh $target "cat /root/.ssh/id_rsa.pub >> ${remote_path}/docker/puppet/authorized_keys.fragment"
# /root/docker-helper-scripts/lib/sh/iptables_starter.sh -l 2>&1 > /dev/null

exit "$?"

which sup's and invokes this script on a freshly minted DO droplet:
/root/docker-helper-scripts/lib/sh/bootstrap_docker.sh
#!/bin/bash
set -x

# https://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/
docker_version=='17.03.0~ce-0~debian-jessie'

function usage () {

  set +x
  echo "$0 <options>"
  echo "This script built 2016-05-24 from recipe provided at"
  echo "https://docs.docker.com/engine/installation/linux/debian/#debian-jessie-80-64-bit"
  echo "    -b : bootstrap docker installation on server, for version $docker_version"
  echo "    -h : show this usage message"
  echo "    -r : remove docker installation"
  echo "    -u : upgrade docker installation"
  echo "    -w : bootstrap a weave installation"
  exit 1

}

function verify_docker_repo_fingerprint () {

  expected_fingerprint='9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88'
  apt-key fingerprint 0EBFCD88 | grep -q "${expected_fingerprint}"
  if [ "$?" -ne 0 ];
  then
    echo 'Expected fingerprint not found for docker apt-get repository'
    echo 'Please investigate: https://docs.docker.com/engine/installation/linux/debian/#install-using-the-repository'
    exit 1
  fi
}

function configure_apt_for_docker () {

  apt-get -y purge lxc-docker*
  apt-get -y purge docker.io*
  apt-get -y purge docker
  apt-get update

  apt-get -y install \
     apt-transport-https \
     ca-certificates \
     curl \
     gnupg2 \
     software-properties-common

  apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
  curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add -
  # verify_docker_repo_fingerprint

  sources=/etc/apt/sources.list.d/docker.list
  # add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
  sources_entry="deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
  echo $sources_entry > $sources

  sources_backport=/etc/apt/sources.list.d/backport.list
  sources_backport_entry='deb http://ftp.debian.org/debian jessie-backports main'
  echo $sources_backport_entry > $sources_backport

  # /root/dhs/lib/sh/iptables_starter.sh
  apt-get update
  apt-cache policy docker-engine
  echo $?

}

function install_and_validate_docker () {

  apt-get update
  docker_version=$(apt-cache show docker-ce | grep Version | head -n1 | sed "s,Version: ,,")
  apt-get -y install docker-ce=${docker_version}
  service docker start
  docker run hello-world
  echo $?

}

function bootstrap_weave_net () {

  which curl 2>&1 > /dev/null
  have_curl=$?
  if [ $have_curl -eq 1 ]; then apt-get -y install curl; fi
  /sbin/iptables -F
  /sbin/iptables -X
  curl -L http://git.io/weave -o /usr/local/bin/weave
  chmod a+x /usr/local/bin/weave
  rc="$?"
  /root/dhs/lib/sh/iptables_starter.sh -L

}

function install_configure_tmux () {
  apt-get -y install tmux
  mkdir -p /var/tmux
}

function upgrade_docker_engine () {

  apt-get upgrade docker-ce

}

function uninstall_docker () {

  apt-get purge docker-ce
  apt-get autoremove

}

function bootstrap_docker () {

  configure_apt_for_docker
  install_and_validate_docker
  bootstrap_weave_net
  install_configure_tmux

}

function main () {

  return

}

while getopts ":bhruw" opt; do
  case $opt in
    b)
      bootstrap_docker
      exit $?
      ;;
    h)
      usage
      ;;
    r)
      uninstall_docker
      exit $?
      ;;
    u)
      upgrade_docker_engine
      exit $?
      ;;
    w)
      bootstrap_weave_net
      exit $?
      ;;
    \?)
      echo "Invalid option: -$OPTARG" >&2
      usage
      ;;
  esac
done

usage
exit $?

and this is the script I use to initialize the firewall:

After running the lib/setup_do_droplet.sh script, I log in and run this:
/root/docker-helper-scripts/lib/sh/bootstrap_docker.sh.
Here is the complete transcript of an end-to-end test:
$ ssh<EMAIL_ADDRESS>
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

root@test-docker-host:~# cd docker-helper-scripts/lib/docker/puppet/
root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ls
authorized_keys.fragment  build.sh  Dockerfile  lib  run-server.sh

root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ./build.sh
./build.sh: line 4: /usr/bin/docker: No such file or directory
root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ../../sh/bootstrap_docker.sh
+ docker_version==17.03.0~ce-0~debian-jessie
+ getopts :bhruw opt
+ usage
+ set +x
../../sh/bootstrap_docker.sh <options>
This script built 2016-05-24 from recipe provided at
https://docs.docker.com/engine/installation/linux/debian/#debian-jessie-80-64-bit
    -b : bootstrap docker installation on server, for version =17.03.0~ce-0~debian-jessie
    -h : show this usage message
    -r : remove docker installation
    -u : upgrade docker installation
    -w : bootstrap a weave installation

root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ../../sh/bootstrap_docker.sh -b

+ docker_version==17.03.0~ce-0~debian-jessie
+ getopts :bhruw opt
+ case $opt in
+ bootstrap_docker
+ configure_apt_for_docker
+ apt-get -y purge 'lxc-docker*'
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lxc-docker*
E: Couldn't find any package by regex 'lxc-docker*'
+ apt-get -y purge 'docker.io*'
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'docker.io' for regex 'docker.io*'
Package 'docker.io' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ apt-get -y purge docker
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'docker' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ apt-get update
Hit http://security.debian.org jessie/updates InRelease
Hit http://security.debian.org jessie/updates/main Sources
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
Ign http://mirrors.digitalocean.com jessie InRelease
Hit http://mirrors.digitalocean.com jessie-updates InRelease
Hit http://mirrors.digitalocean.com jessie Release.gpg
Hit http://mirrors.digitalocean.com jessie-updates/main Sources
Get:1 http://mirrors.digitalocean.com jessie-updates/main amd64 Packages/DiffIndex [7,900 B]
Get:2 http://mirrors.digitalocean.com jessie-updates/main Translation-en/DiffIndex [2,704 B]
Hit http://mirrors.digitalocean.com jessie Release
Hit http://mirrors.digitalocean.com jessie/main Sources
Hit http://mirrors.digitalocean.com jessie/main amd64 Packages
Hit http://mirrors.digitalocean.com jessie/main Translation-en
Fetched 10.6 kB in 4s (2,276 B/s)
Reading package lists... Done
+ apt-get -y install apt-transport-https ca-certificates curl gnupg2 software-properties-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version.
ca-certificates set to manually installed.
curl is already the newest version.
gnupg2 is already the newest version.
gnupg2 set to manually installed.
The following extra packages will be installed:
  gir1.2-glib-2.0 libdbus-glib-1-2 libgirepository-1.0-1 python3-dbus python3-gi python3-software-properties
Suggested packages:
  python-dbus-doc python3-dbus-dbg
The following NEW packages will be installed:
  apt-transport-https gir1.2-glib-2.0 libdbus-glib-1-2 libgirepository-1.0-1 python3-dbus python3-gi python3-software-properties software-properties-common
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,339 kB of archives.
After this operation, 3,119 kB of additional disk space will be used.
Get:1 http://mirrors.digitalocean.com/debian/ jessie/main libdbus-glib-1-2 amd64 0.102-1 [201 kB]
Get:2 http://mirrors.digitalocean.com/debian/ jessie/main apt-transport-https amd64 <IP_ADDRESS>.4 [138 kB]
Get:3 http://mirrors.digitalocean.com/debian/ jessie/main libgirepository-1.0-1 amd64 1.42.0-2.2 [95.7 kB]
Get:4 http://mirrors.digitalocean.com/debian/ jessie/main gir1.2-glib-2.0 amd64 1.42.0-2.2 [141 kB]
Get:5 http://mirrors.digitalocean.com/debian/ jessie/main python3-dbus amd64 1.2.0-2+b3 [189 kB]
Get:6 http://mirrors.digitalocean.com/debian/ jessie/main python3-gi amd64 3.14.0-1 [454 kB]
Get:7 http://mirrors.digitalocean.com/debian/ jessie/main python3-software-properties all 0.92.25debian1 [41.4 kB]
Get:8 http://mirrors.digitalocean.com/debian/ jessie/main software-properties-common all 0.92.25debian1 [79.3 kB]
Fetched 1,339 kB in 2s (580 kB/s)
Selecting previously unselected package libdbus-glib-1-2:amd64.
(Reading database ... 35440 files and directories currently installed.)
Preparing to unpack .../libdbus-glib-1-2_0.102-1_amd64.deb ...
Unpacking libdbus-glib-1-2:amd64 (0.102-1) ...
Selecting previously unselected package apt-transport-https.
Preparing to unpack .../apt-transport-https_<IP_ADDRESS>.4_amd64.deb ...
Unpacking apt-transport-https (<IP_ADDRESS>.4) ...
Selecting previously unselected package libgirepository-1.0-1:amd64.
Preparing to unpack .../libgirepository-1.0-1_1.42.0-2.2_amd64.deb ...
Unpacking libgirepository-1.0-1:amd64 (1.42.0-2.2) ...
Selecting previously unselected package gir1.2-glib-2.0:amd64.
Preparing to unpack .../gir1.2-glib-2.0_1.42.0-2.2_amd64.deb ...
Unpacking gir1.2-glib-2.0:amd64 (1.42.0-2.2) ...
Selecting previously unselected package python3-dbus.
Preparing to unpack .../python3-dbus_1.2.0-2+b3_amd64.deb ...
Unpacking python3-dbus (1.2.0-2+b3) ...
Selecting previously unselected package python3-gi.
Preparing to unpack .../python3-gi_3.14.0-1_amd64.deb ...
Unpacking python3-gi (3.14.0-1) ...
Selecting previously unselected package python3-software-properties.
Preparing to unpack .../python3-software-properties_0.92.25debian1_all.deb ...
Unpacking python3-software-properties (0.92.25debian1) ...
Selecting previously unselected package software-properties-common.
Preparing to unpack .../software-properties-common_0.92.25debian1_all.deb ...
Unpacking software-properties-common (0.92.25debian1) ...
Processing triggers for man-db (<IP_ADDRESS>-5) ...
Processing triggers for dbus (1.8.22-0+deb8u1) ...
Setting up libdbus-glib-1-2:amd64 (0.102-1) ...
Setting up apt-transport-https (<IP_ADDRESS>.4) ...
Setting up libgirepository-1.0-1:amd64 (1.42.0-2.2) ...
Setting up gir1.2-glib-2.0:amd64 (1.42.0-2.2) ...
Setting up python3-dbus (1.2.0-2+b3) ...
Setting up python3-gi (3.14.0-1) ...
Setting up python3-software-properties (0.92.25debian1) ...
Setting up software-properties-common (0.92.25debian1) ...
Processing triggers for libc-bin (2.19-18+deb8u9) ...
Processing triggers for dbus (1.8.22-0+deb8u1) ...
+ apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.H6kTIBf4Y3 --no-auto-check-trustdb --trust-model always --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
gpg: requesting key 2C52609D from hkp server p80.pool.sks-keyservers.net
gpg: key 2C52609D: public key "Docker Release Tool (releasedocker<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
+ curl -fsSL https://download.docker.com/linux/debian/gpg
+ apt-key add -
OK
+ sources=/etc/apt/sources.list.d/docker.list
++ lsb_release -cs
+ sources_entry='deb [arch=amd64] https://download.docker.com/linux/debian jessie stable'
+ echo deb '[arch=amd64]' https://download.docker.com/linux/debian jessie stable
+ sources_backport=/etc/apt/sources.list.d/backport.list
+ sources_backport_entry='deb http://ftp.debian.org/debian jessie-backports main'
+ echo deb http://ftp.debian.org/debian jessie-backports main
+ apt-get update
Ign http://mirrors.digitalocean.com jessie InRelease
Hit http://mirrors.digitalocean.com jessie-updates InRelease
Hit http://security.debian.org jessie/updates InRelease
Hit http://mirrors.digitalocean.com jessie Release.gpg
Hit http://mirrors.digitalocean.com jessie Release
Hit http://mirrors.digitalocean.com jessie-updates/main Sources
Get:1 http://ftp.debian.org jessie-backports InRelease [166 kB]
Get:2 https://download.docker.com jessie InRelease [20.1 kB]
Get:3 http://mirrors.digitalocean.com jessie-updates/main amd64 Packages/DiffIndex [7,900 B]
Get:4 http://mirrors.digitalocean.com jessie-updates/main Translation-en/DiffIndex [2,704 B]
Hit http://security.debian.org jessie/updates/main Sources
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
Hit http://mirrors.digitalocean.com jessie/main Sources
Hit http://mirrors.digitalocean.com jessie/main amd64 Packages
Hit http://mirrors.digitalocean.com jessie/main Translation-en
Get:5 https://download.docker.com jessie/stable amd64 Packages [1,430 B]
Get:6 https://download.docker.com jessie/stable Translation-en_US [587 B]
Get:7 https://download.docker.com jessie/stable Translation-en [584 B]
Get:8 https://download.docker.com jessie/stable Translation-en_US [587 B]
Get:9 https://download.docker.com jessie/stable Translation-en [584 B]
Get:10 https://download.docker.com jessie/stable Translation-en_US [587 B]
Get:11 http://ftp.debian.org jessie-backports/main Translation-en [621 kB]
Get:12 https://download.docker.com jessie/stable Translation-en [584 B]
Get:13 https://download.docker.com jessie/stable Translation-en_US [587 B]
Get:14 http://ftp.debian.org jessie-backports/main amd64 Packages [904 kB]
Get:15 https://download.docker.com jessie/stable Translation-en [584 B]
Get:16 https://download.docker.com jessie/stable Translation-en_US [587 B]
Ign https://download.docker.com jessie/stable Translation-en_US
Get:17 https://download.docker.com jessie/stable Translation-en [584 B]
Ign https://download.docker.com jessie/stable Translation-en
Fetched 1,723 kB in 2s (606 kB/s)
Reading package lists...  Done

++ apt-cache show docker-ce
++ sed 's,Version: ,,'
++ grep Version
++ head -n1
+ docker_version=17.03.1~ce-0~debian-jessie

+ apt-get -y install docker-ce=17.03.1~ce-0~debian-jessie
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  aufs-tools cgroupfs-mount git git-man libapparmor1 libdrm2 liberror-perl libltdl7 libnih-dbus1 libnih1 makedev mountall plymouth
Suggested packages:
  git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn desktop-base plymouth-themes
The following NEW packages will be installed:
  aufs-tools cgroupfs-mount docker-ce git git-man libapparmor1 libdrm2 liberror-perl libltdl7 libnih-dbus1 libnih1 makedev mountall plymouth
0 upgraded, 14 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.6 MB of archives.
After this operation, 114 MB of additional disk space will be used.

(Reading database ... 35651 files and directories currently installed.)
Preparing to unpack .../libdrm2_2.4.58-2_amd64.deb ...
Unpacking libdrm2:amd64 (2.4.58-2) ...
Selecting previously unselected package libltdl7:amd64.
Preparing to unpack .../libltdl7_2.4.2-1.11+b1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.2-1.11+b1) ...
Selecting previously unselected package makedev.
Preparing to unpack .../makedev_2.3.1-93_all.deb ...
Unpacking makedev (2.3.1-93) ...
Selecting previously unselected package plymouth.
Preparing to unpack .../plymouth_0.9.0-9_amd64.deb ...
Unpacking plymouth (0.9.0-9) ...
Selecting previously unselected package libnih1.
Preparing to unpack .../libnih1_1.0.3-4.3_amd64.deb ...
Unpacking libnih1 (1.0.3-4.3) ...
Selecting previously unselected package libnih-dbus1.
Preparing to unpack .../libnih-dbus1_1.0.3-4.3_amd64.deb ...
Unpacking libnih-dbus1 (1.0.3-4.3) ...
Selecting previously unselected package mountall.
Preparing to unpack .../mountall_2.54_amd64.deb ...
Unpacking mountall (2.54) ...
Selecting previously unselected package aufs-tools.
Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1_amd64.deb ...
Unpacking aufs-tools (1:3.2+20130722-1.1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../cgroupfs-mount_1.1_all.deb ...
Unpacking cgroupfs-mount (1.1) ...
Selecting previously unselected package libapparmor1:amd64.
Preparing to unpack .../libapparmor1_2.9.0-3_amd64.deb ...
Unpacking libapparmor1:amd64 (2.9.0-3) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_17.03.1~ce-0~debian-jessie_amd64.deb ...
Unpacking docker-ce (17.03.1~ce-0~debian-jessie) ...
Selecting previously unselected package liberror-perl.
Preparing to unpack .../liberror-perl_0.17-1.1_all.deb ...
Unpacking liberror-perl (0.17-1.1) ...
Selecting previously unselected package git-man.
Preparing to unpack .../git-man_1%3a2.1.4-2.1+deb8u3_all.deb ...
Unpacking git-man (1:2.1.4-2.1+deb8u3) ...
Selecting previously unselected package git.
Preparing to unpack .../git_1%3a2.1.4-2.1+deb8u3_amd64.deb ...
Unpacking git (1:2.1.4-2.1+deb8u3) ...
Processing triggers for man-db (<IP_ADDRESS>-5) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for dbus (1.8.22-0+deb8u1) ...
Setting up libdrm2:amd64 (2.4.58-2) ...
Setting up libltdl7:amd64 (2.4.2-1.11+b1) ...
Setting up makedev (2.3.1-93) ...
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
Setting up plymouth (0.9.0-9) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up libnih1 (1.0.3-4.3) ...
Setting up libnih-dbus1 (1.0.3-4.3) ...
Setting up mountall (2.54) ...
Setting up aufs-tools (1:3.2+20130722-1.1) ...
Setting up cgroupfs-mount (1.1) ...
Setting up libapparmor1:amd64 (2.9.0-3) ...
Setting up docker-ce (17.03.1~ce-0~debian-jessie) ...
Setting up liberror-perl (0.17-1.1) ...
Setting up git-man (1:2.1.4-2.1+deb8u3) ...
Setting up git (1:2.1.4-2.1+deb8u3) ...
Processing triggers for libc-bin (2.19-18+deb8u9) ...
Processing triggers for systemd (215-17+deb8u7) ...
Processing triggers for initramfs-tools (0.120+deb8u3) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
Processing triggers for dbus (1.8.22-0+deb8u1) ...

+ service docker start
+ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
78445dd45222: Pull complete
Digest: sha256:c5515758d4c5e1e838e9cd307f6c6a0d620b5e07e6f927b07d05f6d12a1ac8d7
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://cloud.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/engine/userguide/

+ echo 0
0
+ bootstrap_weave_net
+ which curl
+ have_curl=0
+ '[' 0 -eq 1 ']'
+ /sbin/iptables -F
+ /sbin/iptables -X
+ curl -L http://git.io/weave -o /usr/local/bin/weave
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   578    0   578    0     0   1514      0 --:--:-- --:--:-- --:--:--  1514
100 77117  100 77117    0     0   138k      0 --:--:-- --:--:-- --:--:--  138k
+ chmod a+x /usr/local/bin/weave
+ rc=0
+ /root/dhs/lib/sh/iptables_starter.sh -L
../../sh/bootstrap_docker.sh: line 90: /root/dhs/lib/sh/iptables_starter.sh: No such file or directory
+ install_configure_tmux
+ apt-get -y install tmux
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  tmux
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 245 kB of archives.
After this operation, 610 kB of additional disk space will be used.
Get:1 http://mirrors.digitalocean.com/debian/ jessie/main tmux amd64 1.9-6 [245 kB]
Fetched 245 kB in 0s (381 kB/s)
Selecting previously unselected package tmux.
(Reading database ... 36858 files and directories currently installed.)
Preparing to unpack .../archives/tmux_1.9-6_amd64.deb ...
Unpacking tmux (1.9-6) ...
Processing triggers for man-db (<IP_ADDRESS>-5) ...
Setting up tmux (1.9-6) ...
+ mkdir -p /var/tmux
+ exit 0

root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                     PORTS               NAMES
e75808ccb079        hello-world         "/hello"            3 minutes ago       Exited (0) 3 minutes ago                       frosty_shannon

root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ./build.sh
Sending build context to Docker daemon 27.14 kB
Step 1/16 : FROM phusion/baseimage:0.9.19
0.9.19: Pulling from phusion/baseimage
f069f1d21059: Pull complete
ecbeec5633cf: Pull complete
ea6f18256d63: Pull complete
54bde7b02897: Pull complete
a3ed95caeb02: Pull complete
ce9e695a6234: Pull complete
346026b9659b: Pull complete
Digest: sha256:73cfb8db14843adf4797fda5b663650a1390466cdf94d39cfc178a42c0ef4767
Status: Downloaded newer image for phusion/baseimage:0.9.19
 ---> c39664f3d4e5
Step 2/16 : ENV HOME /root
 ---> Running in 91775e52a63a
 ---> ac6fbfe2130e
Removing intermediate container 91775e52a63a
Step 3/16 : RUN rm -f /etc/service/sshd/down
 ---> Running in 673683c5e40f
 ---> 5a29c08ca432
Removing intermediate container 673683c5e40f
Step 4/16 : RUN cat /etc/my_init.d/00_regen_ssh_host_keys.sh
 ---> Running in 8942e91e0c37
#!/bin/bash
set -e
if [[ ! -e /etc/service/sshd/down && ! -e /etc/ssh/ssh_host_rsa_key ]] || [[ "$1" == "-f" ]]; then
	echo "No SSH host key available. Generating one..."
	export LC_ALL=C
	export DEBIAN_FRONTEND=noninteractive
	dpkg-reconfigure openssh-server
fi
 ---> f706dd41ef5e
Removing intermediate container 8942e91e0c37
Step 5/16 : RUN /etc/my_init.d/00_regen_ssh_host_keys.sh
 ---> Running in 47a17799a49e
No SSH host key available. Generating one...
Creating SSH2 RSA key; this may take some time ...
2048 SHA256:fImo9pOGwSd0PqZrUREulxv2dcdrLnGjJefhhZNVV84 root@721c971d0d37 (RSA)
Creating SSH2 DSA key; this may take some time ...
1024 SHA256:E2sZFB27dHoFaj83vsTpMIGqluhPWNzbQyNu1MeRsKw root@721c971d0d37 (DSA)
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:3D2ZpZjBKRQ/qVDcM/3N0bMYd3cLxGo5UIyUAxJU8ZU root@721c971d0d37 (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:ny+Q3HaM9zy/YmzAZ0ufWlwdFy4CGLqUvp/eXXqzJio root@721c971d0d37 (ED25519)
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of restart.
 ---> c8e81bd8b180
Removing intermediate container 47a17799a49e
Step 6/16 : ADD authorized_keys.fragment /tmp/authorized_keys.fragment
 ---> f2fd4c0c1ab2
Removing intermediate container 51933297f6f1
Step 7/16 : RUN cat /tmp/authorized_keys.fragment >> /root/.ssh/authorized_keys && rm -f /tmp/authorized_keys.fragment
 ---> Running in e92aac09ea32
 ---> af3c4839824d
Removing intermediate container e92aac09ea32
Step 8/16 : RUN /bin/ln -s /root/.ssh/authorized_keys /root/.ssh/authorized_keys2
 ---> Running in f740bb6b1ed2
 ---> cbdd63674091
Removing intermediate container f740bb6b1ed2
Step 9/16 : RUN ls -alht /root/.ssh
 ---> Running in b6cf0ac50a18
total 12K
drwx------ 2 root root 4.0K May 24 01:30 .
drwx------ 6 root root 4.0K May 24 01:30 ..
lrwxrwxrwx 1 root root   26 May 24 01:30 authorized_keys2 -> /root/.ssh/authorized_keys
-rw-r--r-- 1 root root 1.2K May 24 01:30 authorized_keys
 ---> a8ceed187900
Removing intermediate container b6cf0ac50a18
Step 10/16 : RUN /bin/sed -i "s,#PermitRootLogin yes,PermitRootLogin yes," /etc/ssh/sshd_config
 ---> Running in 784a826ebf92
 ---> 16087ed04dbe
Removing intermediate container 784a826ebf92
Step 11/16 : ENTRYPOINT /bin/sh -c echo '<IP_ADDRESS>  archive.ubuntu.com' >> /etc/hosts && echo '<IP_ADDRESS>  archive.ubuntu.com' >> /etc/hosts && exec /sbin/my_init
 ---> Running in f9cc268bf8d8
 ---> 7ec729334b6d
Removing intermediate container f9cc268bf8d8
Step 12/16 : RUN /usr/bin/touch /etc/docker_container
 ---> Running in 0e71ec37b697
 ---> b56aefa1a62a
Removing intermediate container 0e71ec37b697
Step 13/16 : RUN /bin/mkdir -p /root/lib/sh
 ---> Running in 953ba8028f3d
 ---> c3f9280809b4
Removing intermediate container 953ba8028f3d
Step 14/16 : ADD lib/sh/deploy-puppet-on-debian.sh /root/lib/sh/deploy-puppet-on-debian.sh
 ---> 9dd539acb50d
Removing intermediate container 5a4ae6f82a7c
Step 15/16 : RUN /etc/init.d/ssh restart
 ---> Running in b3c6eb4f5761
 * Restarting OpenBSD Secure Shell server sshd
   ...done.
 ---> 03e3d9100ab4
Removing intermediate container b3c6eb4f5761
Step 16/16 : RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
 ---> Running in caa3d74bd8f0
 ---> ac93ec3c0a07
Removing intermediate container caa3d74bd8f0
Successfully built ac93ec3c0a07
root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ./run-server.sh
8a32f6c4af52e24233723953d7a6a77bfcf66282b2714a5d795b0c9bf50aa90e

root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# docker inspect puppet-agent | grep IPAddress
            "SecondaryIPAddresses": null,
            "IPAddress": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
root@test-docker-host:~/docker-helper-scripts/lib/docker/puppet# ssh <IP_ADDRESS>
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is 30:5c:b2:23:d3:5b:0d:82:e6:00:d0:89:67:2d:b5:da.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.

root@puppet-agent:/# apt-get update
Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Could not connect to archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
Err:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Unable to connect to archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
Err:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease
  Unable to connect to archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Could not connect to archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Unable to connect to archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Unable to connect to archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@puppet-agent:/#

root@puppet-agent:/# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

cat Dockerfile
FROM phusion/baseimage:0.9.19
ENV HOME /root
RUN rm -f /etc/service/sshd/down
RUN cat /etc/my_init.d/00_regen_ssh_host_keys.sh
RUN /etc/my_init.d/00_regen_ssh_host_keys.sh
ADD authorized_keys.fragment /tmp/authorized_keys.fragment
RUN cat /tmp/authorized_keys.fragment >> /root/.ssh/authorized_keys && rm -f /tmp/authorized_keys.fragment
RUN /bin/ln -s /root/.ssh/authorized_keys /root/.ssh/authorized_keys2
RUN ls -alht /root/.ssh
RUN /bin/sed -i "s,#PermitRootLogin yes,PermitRootLogin yes," /etc/ssh/sshd_config
ENTRYPOINT ["/bin/sh", "-c" , "echo '<IP_ADDRESS>  archive.ubuntu.com' >> /etc/hosts && echo '<IP_ADDRESS>  archive.ubuntu.com' >> /etc/hosts && exec /sbin/my_init" ]
RUN /usr/bin/touch /etc/docker_container
RUN /bin/mkdir -p /root/lib/sh
ADD lib/sh/deploy-puppet-on-debian.sh /root/lib/sh/deploy-puppet-on-debian.sh
RUN /etc/init.d/ssh restart
RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

getting similar issues here, unable to apt-get install packages due to DNS resolution not working, when i switch to ubuntu:16.04 as the base image it works fine

i deleted the baseimage from my docker cache 0.9.22, re-pulled it, tweaked my Dockerfile a bit following the instructions on the README, and it seems to work now with apt-get installing the packages

Thank you @alan-czajkowski for the solution! Could you please provide a bit more specifics? Thanks!

@Theaxiom looks like I spoke too soon, it seems to only intermittently work, here is what occasionally works (apt-get fails occassionally):
FROM phusion/baseimage:0.9.22

# Use baseimage-docker's init system
CMD [ "/sbin/my_init" ]

RUN apt-get update \
 && apt-get install -y \
    zip \
    curl \
    wget

ENV DEBIAN_FRONTEND "noninteractive"

# Clean up APT when done
RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

Is this only affecting 0.9.22 or have you tried other versions?

@Theaxiom I'm not sure, I've been using 0.9.19 for a while with my past projects, and only recently moved to 0.9.22 for my new projects, and then these weird issues began.
My ultimate goal is to create a NodeJS docker image, essentially take this:
https://github.com/nodejs/docker-node/blob/12ba2e5432cd50037b6c0cf53464b5063b028227/8.1/Dockerfile
and replace
FROM buildpack-deps:jessie

with
FROM phusion/baseimage:0.9.22

If someone can get that working then let me know.

the docker version has changed drastically too, so I'm not sure what the issue really is

I think I know what the problem is. I'm running latest version of Docker (17.03) on OS X (10.10.5). When you put your MacBook to sleep, docker-machine is not able to recover properly from a wakeup. You have to
docker-machine restart

to get things to start to work again. It's pretty frustrating, but I believe that could be the issue.

I am not using a Mac but a recent Debian on bare metal (or on a digital ocean droplet for my tests).  Alan has version 0.9.22, I was using version 0.9.19.  Was still facing issues last time I tested this.

From my experience Docker is extremely buggy unless you use a proven and
tested version. To know which one is that, have a look at container Linux's
stable version. Right now it's 1.12.6.
It word reliability on OS X and has a special, commercially supported LTS
version for most Linux. The cs version is freely available.
On 2017. Jun 22., Thu at 1:39, Hugh Esco<EMAIL_ADDRESS>wrote:

I am not using a Mac but a recent Debian on bare metal (or on a digital
ocean droplet for my tests). Alan has version 0.9.22, I was using version
0.9.19. Was still facing issues last time I tested this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/issues/412#issuecomment-310234837,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj7sQ6D5i23WJY32xdTDHqLolKXBEks5sGanNgaJpZM4NhuwX
.

+1 for ContainerLinux AKA CoreOS


m_dwLocalPlayer broken

I've opened a pull request which should fix this.

@jgarofolo thanks ya Bro.


Add write_electrical_series option to write_recording

Fix https://github.com/catalystneuro/nwb-conversion-tools/pull/368
Motivation
Add write_electrical_series option to write_recording to optionally avoid writing time series .
How to test the behavior?
write_recording(..., write_electrical_series=False)

Checklist

[x] Have you checked our Contributing document?
[x] Have you ensured the PR description clearly describes the problem and solutions?
[x] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
[x] If this PR fixes an issue, is the first line of the PR description fix #XXX where XXX is the issue number?

@alejoe91 This being an alternative to directly calling
add_device(recording=recording, nwbfile=nwbfile, metadata=metadata)
add_electrode_groups(...)
add_electrodes(...)

which itself could be wrapped into a function (add_electrode_info or something like that) to reduce lines of code, with the main difference being that for your changes, the nwbfile object is also created or opened at the same time?
I assume this is building towards a way of specifying electrode information for SortingInterfaces in advance of the WaveformExtractor incorporation?

@alejoe91 A couple other things

[ ] Can you add a test for this new option?
[ ] Whenever we add these kind of arguments to write_recording we usually propagate them up to the DataInterface levels. Can you do that as well? (should only require adding it to BaseRecordingDataInterface)

@alejoe91 This being an alternative to directly calling
add_device(recording=recording, nwbfile=nwbfile, metadata=metadata)
add_electrode_groups(...)
add_electrodes(...)

which itself could be wrapped into a function (add_electrode_info or something like that) to reduce lines of code, with the main difference being that for your changes, the nwbfile object is also created or opened at the same time?
I assume this is building towards a way of specifying electrode information for SortingInterfaces in advance of the WaveformExtractor incorporation?

@CodyCBakerPhD I made an extra function (add_device_electrode_info). However I think that it's more user friendly to keep the write_electrical_series option in the write_recording instead of creatung a new write_ function.

@CodyCBakerPhD applied suggested changes. Can you accept and merge?


Cursor animation is on by default and cannot be turned off

Probably caused by https://github.com/microsoft/vscode/pull/169113
Cursor animation is turned on in main regardless of the value of editor.cursorSmoothCaretAnimation

confirming the bug. partially solved by setting cursorSmoothCaretAnimation to explicit

Sorry about this, working on a fix!

as a temporary workaround you can inject this style with devtools to get rid of the animation:
.cursor { transition: none !important }


Removed "Produce - no acks required" test

What does this PR do?
Revert https://github.com/DataDog/datadog-agent/pull/28944.

Motivation
This test turned to be highly flaky, so we'll remove it for now.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


unknown feature llvm_asm

$ capsule build --release
Building contract nft-validator
   Compiling ckb-std v0.9.0
error[E0635]: unknown feature `llvm_asm`
  --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/ckb-std-0.9.0/src/lib.rs:12:12
   |
12 | #![feature(llvm_asm)]
   |            ^^^^^^^^

For more information about this error, try `rustc --explain E0635`.
error: could not compile `ckb-std` due to previous error
error: docker container exit with code Some(101)

$ capsule --version
Capsule 0.8.0

$ ckb-cli --version
ckb-cli 0.103.0 (1dd9cd7 2022-05-27)

Please also provide your capsule.toml file, since the docker image which used to build the project is matter.

# [rust]
# # path of rust contracts workspace directory,
# # a `Cargo.toml` file is expected under the directory.
# workspace_dir = "."
# toolchain = "nightly-2021-12-25"
# docker_image = "thewawar/ckb-capsule:2021-12-25"

# capsule version
version = "0.8.0"
# path of deployment config file
deployment = "deployment.toml"

[[contracts]]
name = "nft-validator"
template_type = "Rust"

The default docker image used in capsule v0.8.0 is thewawar/ckb-capsule:2022-08-01 which use toolchain nightly-2022-08-01, and this rustc don't recognize #![feature(llvm_asm)], since this feature is already removed now.
You may have three choice:

downgrade capsule from v0.8.0 to v0.7.3
keep using capsule v0.8.0, and upgrade ckb-std from v0.9.0 to v0.10.0
keep using capsule v0.8.0, and change capsule.toml to (uncomment the [rust] section):

[rust]
# path of rust contracts workspace directory,
# a `Cargo.toml` file is expected under the directory.
workspace_dir = "."
toolchain = "nightly-2021-12-25"
docker_image = "thewawar/ckb-capsule:2021-12-25"

# capsule version
version = "0.8.0"
# path of deployment config file
deployment = "deployment.toml"

[[contracts]]
name = "nft-validator"
template_type = "Rust"

The default docker image used in capsule v0.8.0 is thewawar/ckb-capsule:2022-08-01 which use toolchain nightly-2022-08-01, and this rustc don't recognize #![feature(llvm_asm)], since this feature was already removed now.
You may have three choice:

downgrade capsule from v0.8.0 to v0.7.3
keep using capsule v0.8.0, and upgrade ckb-std from v0.9.0 to v0.10.0
keep using capsule v0.8.0, and change capsule.toml to (uncomment the [rust] section):

[rust]
# path of rust contracts workspace directory,
# a `Cargo.toml` file is expected under the directory.
workspace_dir = "."
toolchain = "nightly-2021-12-25"
docker_image = "thewawar/ckb-capsule:2021-12-25"

# capsule version
version = "0.8.0"
# path of deployment config file
deployment = "deployment.toml"

[[contracts]]
name = "nft-validator"
template_type = "Rust"

Thanks very much.

May I ask how to upgrade ckb-std from v0.9.0 to v0.10.0?

I’ve downgrade capsule from v0.8.0 to v0.7.3, and it looks good. But there is another problem when I deploy contract.
$ capsule deploy --address ckt1qyqw8yx5hx6vwcm7eqren0d0v39wvfwdhy3q2807pp --fee 0.01
thread 'main' panicked at 'rpc call get_block_by_number: error decoding response body: EOF while parsing a value at line 1 column 0

Caused by:
    EOF while parsing a value at line 1 column 0', src/wallet/rpc.rs:157:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Do you have a ckb node started? If your ckb node can't access through the default url (which is http://localhost:8114), above error will happen.
You may use capsule deploy --api <url> ... to specific the ckb node url.

I start ckb node in this way:
git clone https://github.com/cryptape/lumos-ckit-internal.git
cd lumos-ckit-internal/devtools/docker
docker compose up --build

And there is still problem after I specify the ckb node url:
$ capsule deploy --address ckt1qyqw8yx5hx6vwcm7eqren0d0v39wvfwdhy3q2807pp --fee 0.01 --api http://localhost:8114
thread 'main' panicked at 'rpc call get_block_by_number: error decoding response body: EOF while parsing a value at line 1 column 0

Caused by:
    EOF while parsing a value at line 1 column 0', src/wallet/rpc.rs:157:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

You can use follow commands to the test the url:
# test if there is a server bind to this address
curl http://localhost:8114

# test if the server is ckb node
ckb-cli --url http://localhost:8114 rpc get_tip_header

$ ckb-cli --url http://localhost:8114 rpc get_tip_header
compact_target: 0x20010000
dao: 0xaa779abd8dbce7a26765087a2f3824007b152f821f38e302007d7ad95622ff06
epoch: "0x20001000ddc {number: 3548, index: 1, length: 2}"
extra_hash: 0x0000000000000000000000000000000000000000000000000000000000000000
hash: 0xff3675d821a7a2ba0403fd12cea893bd450e2ba24ecba60dfc2e815cf1efbc10
nonce: 0x53d3f7614fa2f23453e2eb992840dec2
number: 7097
parent_hash: 0x0d66a5738c878049cebf129414fbf92e9267dede90c236a2a0ceeaaee4d79220
proposals_hash: 0x0000000000000000000000000000000000000000000000000000000000000000
timestamp: "1661833627662 (2022-08-30 12:27:07.662 +08:00)"
transactions_root: 0x5716c17fa721d5e228427e50feba4e65bab3c4ef9735ec8165753780cb18658c
version: 0

$ curl http://localhost:8114
Used HTTP Method is not allowed. POST or OPTIONS is required

That is strange, the above error happen when rpc client get the genesis block, you may use ckb-cli to test if you can get genesis block:
ckb-cli --url http://localhost:8114  rpc get_block_by_number --number 0

That is strange, the above error happen when rpc client get the genesis block, you may use ckb-cli to test if you can get genesis block:
ckb-cli --url http://localhost:8114  rpc get_block_by_number --number 0

It seems I can get genesis block:
...
   outputs:
      - capacity: "117.0"
        lock:
          args: 0x
          code_hash: 0x0000000000000000000000000000000000000000000000000000000000000000
          hash_type: data
        type: ~
      - capacity: "117.0"
        lock:
          args: 0x
          code_hash: 0x0000000000000000000000000000000000000000000000000000000000000000
          hash_type: data
        type: ~
    outputs_data:
      - 0x02000000f1e9baa862d4c61ccdea49a810a406c47416b2eb92df7e9eac88852c0696bcbd03000000f1e9baa862d4c61ccdea49a810a406c47416b2eb92df7e9eac88852c0696bcbd01000000
      - 0x02000000f1e9baa862d4c61ccdea49a810a406c47416b2eb92df7e9eac88852c0696bcbd03000000f1e9baa862d4c61ccdea49a810a406c47416b2eb92df7e9eac88852c0696bcbd04000000
    version: 0
    witnesses:
      - 0xd84055193b4c5278f22bc6c2aa6f50ff046547f9a7bb2ff6747c3b235a131aa83270847006f57a04970abfe854198a4b2ea9e369598f3cd44d2ea22d8efc30e701
uncles: []

I have no clue now, I believe this is a network issue that can reproduce with ckb-cli:
$ ckb-cli --url http://localhost:3333 rpc get_block_by_number --number 0
http error: `error decoding response body: EOF while parsing a value at line 1 column 0`

My output looks different from yours:
$ ckb-cli --url http://localhost:3333 rpc get_block_by_number --number 0
http error: `error sending request for url (http://localhost:3333/): error trying to connect: tcp connect error: Connection refused (os error 111)`

It works after removing the proxy.


System.UnauthorizedAccessException: Access to the path "...." is denied when getting the stream of some files on Android

Expected Behavior
Should be able to use any file on Android
Actual Behavior
Files with such problem can reside in different directories. Some files might work others might not in the same directory.
03-25 12:26:02.039 E/mono-rt ( 1937): System.UnauthorizedAccessException: Access to the path "/storage/emulated/0/Download/leroy.txt" is denied.
03-25 12:26:02.039 E/mono-rt ( 1937):   at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x001aa] in /Users/builder/jenkins/workspace/archive-mono/2019-10/android/release/mcs/class/corlib/System.IO/FileStream.cs:239
03-25 12:26:02.039 E/mono-rt ( 1937):   at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share) [0x00000] in /Users/builder/jenkins/workspace/archive-mono/2019-10/android/release/mcs/class/corlib/System.IO/FileStream.cs:91
03-25 12:26:02.039 E/mono-rt ( 1937):   at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
03-25 12:26:02.039 E/mono-rt ( 1937):   at System.IO.File.OpenRead (System.String path) [0x00000] in /Users/builder/jenkins/workspace/archive-mono/2019-10/android/release/external/corefx/src/System.IO.FileSystem/src/System/IO/File.cs:266
03-25 12:26:02.039 E/mono-rt ( 1937):   at Plugin.FilePicker.FilePickerImplementation+<>c__DisplayClass5_1.<PickFileAsync>b__2 () [0x00034] in D:\a\1\s\src\Plugin.FilePicker\Android\FilePickerImplementation.android.cs:114
03-25 12:26:02.039 E/mono-rt ( 1937):   at Plugin.FilePicker.Abstractions.FileData.GetStream () [0x0000f] in D:\a\1\s\src\Plugin.FilePicker\FileData.shared.cs:156

Steps to Reproduce the Problem

Pick the file
Call GetStream on FileData

Specifications

NuGet package version: 2.1.41-beta
Platform(s): Xamarin.Forms 4.5; Android 10

Discussion
It looks like this issue happens when target SDK is Android 10. Tested on the device with Android 10 as well (not sure about devices with lower version).
It might be related to newly introduced Scoped storage.
Few resources which might be helpful:
https://github.com/xamarin/xamarin-android/issues/3426#issuecomment-579045662
https://www.youtube.com/watch?v=UnJ3amzJM94
I noticed that this exception happens when we find a local Uri (and not just using content Uri) https://github.com/jfversluis/FilePicker-Plugin-for-Xamarin-and-Windows/blob/8e1813cb55440a1e542d3c1437a183a4f326451e/src/Plugin.FilePicker/Android/FilePickerActivity.android.cs#L168
and then are using
https://github.com/jfversluis/FilePicker-Plugin-for-Xamarin-and-Windows/blob/8e1813cb55440a1e542d3c1437a183a4f326451e/src/Plugin.FilePicker/Android/FilePickerImplementation.android.cs#L114
instead of
https://github.com/jfversluis/FilePicker-Plugin-for-Xamarin-and-Windows/blob/8e1813cb55440a1e542d3c1437a183a4f326451e/src/Plugin.FilePicker/Android/FilePickerImplementation.android.cs#L110
Why should we use local paths at all? Can we always use content Uri and OpenInputStream?
Quick fix
Add android:requestLegacyExternalStorage="true" to application tag in manifest

The whole code to try to resolve a content:// URI to a file path was there from the beginning. My guess is that FilePicker users insisted on getting a file path on the picked file, even when it goes against Android's model. Maybe we should skip those efforts when running on Android 10 and above. We are happy to accept any PR that you can come up for us. Thanks!

Thanks Great its(android:requestLegacyExternalStorage="true") working for me as well in android 10

Can confirm the same issue and the quick fix suggest also works for me.

Please be aware that:

Caution: After you update your app to target Android 11 (API level 30), the system ignores the requestLegacyExternalStorage attribute when your app is running on Android 11 devices, so your app must be ready to support scoped storage and to migrate app data for users on those devices.
See here.

We urge a fix in the plugin code I guess. And i guess it all boils down to GetExternalStoragepublicDirectory being deprecated in Android Q.

We always welcome patches and pull requests! So of you are able to come up with a fix, just propose it. Thanks!

I just proposed a fix via PR. I was able to test it in my own project and it works fine. The change is simple, maybe too simple even. I'm happy to make adjustments if needed.


nixos/zfs: add keyScript option

Description of changes
Adds boot.zfs.keyScripts and boot.initrd.clevis options to automatically unlock zfs natively-encrypted partitions at boot.
Motivation
Previously, dataset credentials were only able to be provided through a file on disk or a prompted password. This is problematic for systems which want to make use of tools such as clevis to bind datasets to TPMs.
Clevis is included in this PR as a reference example.
These changes introduce the concepet of key scripts, which are run before attempting an interactive password prompt and are able to unlock the dataset.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I am interested into this and will take time to do a full review as well. I am currently trying to write testing for this.

@JulienMalka Given the existence of your Clevis & Tang PR, can I entrust you to drive this PR now? I think the ZFS stuff is still very cool for TPM2 usecases (or Clevis), I would maybe rather introduce TPM2 usecases directly too to support TPM2 based unlock of ZFS rootfs which is impossible with systemd-cryptenroll at the moment because it only supports cryptsetup.

@HexF Thank you of this PR. Can we maybe try to make it integrate neatly with #257525? My vision is that your keyscript option will allow for more general zfs unlocking than clevis does. In order to make it mergeable I'd remove all clevis related stuff and keep only the keyscript option. In a second time we can use your keyscript implementation to unlock zfs datasets with clevis. I see that you have an implementation for systemd stage 1, could you add one for scripted initrd?


Duplicate instafeed

Sorted out the issue, had nothing to do with instafeed.js :)

You can close the issue then :)


[SPARK-7011] Build(compilation) fails with scala 2.11 option, because a protected[sql] type is accessed in ml package.

This is where it is used and fails compilations at.

Test build #30586 has started for   PR 5593 at commit e6d57a3.

Seems OK to me.

@mengxr and @marmbrus PTAL.

Test build #30586 has finished for   PR 5593 at commit e6d57a3.

This patch passes all tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

protected[spark] abstract class NativeType extends DataType

This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30586/
Test PASSed.

This is fine to fix the build break, but ideally MLlib would not rely on this internal detail (that I'd like to remove).  @mengxr, what are you guys using this for?

Thanks, merged to master.
@mengxr, we should figure out how you are using NativeType as I would like to get rid of it.


[Help] : Replace underscore with space

When downloading mangas the space in the name of the manga folder gets replaced by _ .How do I change and his behavior ,I couldn't find that option in the config

Hi! Will add an option to change that in the next release

Thanks


Avatar doesn't display if changed in Twitter after first dashboard login

I believe you are aware of this issue already, but good to get it added in here :)

Fixed (to a certain extent) in v1.0.2. Logging in will refresh the app info (including profile urls).


Error: false is not a string. when repo_version is not set

repo_version is initialized to false.
$manage_repo           = false,
$repo_version          = false,
$logging_file          = undef,
init.pp line 258 tests if repo_version is a string
if ($manage_repo == true) {
validate_string($repo_version)
}
if repo_version is not set then puppet reports error: Error: false is not a string.  It looks to be a FalseClass at elasticsearch/manifests/init.pp:258
I was confused when I saw the error message at first. shouldn't repo_version be set to undef or empty string?

With https://github.com/elasticsearch/puppet-elasticsearch/pull/252 I've added a more human friendly error message.


add proxy support

hello
it is very important feature.
for example https://bitbucket.org/pypa/bandersnatch/issue/59/proxy-please

hello
any news about this pr ?

Any updates? This patch would allow the use of proxies, which would be invaluable for corporate networks.

Hello,
Just tested this release as it is a major blocker for a project.
It works fine.
Can this be moved forward ?

Hi @dstufft we are also looking to use this feature - is there anything we can do to help this progress into the master branch? Does it need reworking to pass the checks and it can then be merged in?
Thanks

Very important feature for bandersnatch to work behind proxy server.


No menu

Menu not loaded up

please provide logs with android version

Not on PC rn, logs say something Lib not found when its there. Wait.. does it need to be matched x86_64 lib if test on LD9?

Not on PC rn, logs say something Lib not found when its there. Wait.. does it need to be matched x86_64 lib if test on LD9?

oh just load the lib from anywhere elso like /tmp or /sdcard any other path like this
but don't use apk's private folders like data dir or lib dir because it woun't worked with Yukki idk why but you can load the lib from anywhere else before calling the menu if you need that feature then make a feature request

Not on PC rn, logs say something Lib not found when its there. Wait.. does it need to be matched x86_64 lib if test on LD9?

oh just load the lib from anywhere elso like /tmp or /sdcard any other path like this
but don't use apk's private folders like data dir or lib dir because it woun't worked with Yukki idk why but you can load the lib from anywhere else before calling the menu if you need that feature then make a feature request

It sends the context of the hooked application. The hooked application can't load library from another application so it fails.


Update typescript-formatter and add tsx support

What does this implement/fix? Explain your changes.
Updates typescript-formatter to latest version, along with necessary change in coffeescript file. Also adds support for TSX language and typescript-formatter ability to format it.
...
Does this close any currently open issues?
#601 #1977
...
Any other comments?
...
Checklist
Check all those that are applicable and complete.

[X] Merged with latest master branch
[X] Regenerate documentation with npm run docs
[X] Add change details to CHANGELOG.md under "Next" section
[x] Added examples for testing to examples/ directory
[X] Travis CI passes (Mac support)
[X] AppVeyor passes (Windows support)

@Glavin001  Please add a version with this :)

I should publish this weekend. I want to merge a few more Pull Requests and need some more time to review 😃 . Thank you for your reminder and interest! I will post here once I've published the next release.

Published to v0.32.0

Thanks :)


Minor bugs

I'm just flagging that I'm aware of a couple of bugs .. inverted images and color runs at the end of images aren't being filled.
Both these have been fixed but the upload won't happen for about 10hrs (while I sleep).

Should be fixed now.


Method for getting cash that is locked in open orders

I can't seem to find a method in the API for getting the quantity of cash that is already locked in open orders (i.e. need to cancel them to free up the cash for a new order). Most crypto APIs have a method to get account balances that includes free (available) and locked (used in orders) balances. For example Binance may respond with this:
{
  "asset": "ETH",
  "free": "6.89208129",
  "locked": "0.14702384"
},

I expect to have a similar thing for forex.
Expected Behavior
Have a method in API for retrieving the cash quantities that are locked in open orders.
Actual Behavior
Need to calculate it, that may be error prone.
Potential Solution
I came up with the following solution but I'm not sure it is 100% correct.
public void OnData(QuoteBars data)
{
    LimitOrder("EURUSD", 500, 0.5m);
    var usedQuantities = GetQuantitiesLockedInOpenOrders();
}

/// <summary>
/// Gets quantities locked in open orders.
/// </summary>
/// <returns>A dictionary of portfolio cash and their locked quantities.</returns>
public Dictionary<string, decimal> GetQuantitiesLockedInOpenOrders()
{
    var usedQuantities = new Dictionary<string, decimal>();

    foreach (var orderTicket in Transactions.GetOpenOrderTickets())
    {
        var orderDirection = Transactions.GetOpenOrders(order => order.Id == orderTicket.OrderId).First().Direction; // example: Buy
        var symbol = orderTicket.Symbol; // example: EURUSD
        var quoteAsset = Securities[symbol].QuoteCurrency.Symbol; // example: USD
        var baseAsset = symbol.Value.Split('/')[0]; // example: EURUSD
        if (orderTicket.SecurityType == SecurityType.Forex ||
            orderTicket.SecurityType == SecurityType.Crypto)
        {
            // remove quoteAsset from end of baseAsset
            if (baseAsset.EndsWith(quoteAsset))
            {
                baseAsset = baseAsset.Remove(baseAsset.LastIndexOf(quoteAsset, StringComparison.Ordinal)); // example: EUR
            }
        }
        // asset with some quantity locked in the order
        var usedAsset = orderDirection == OrderDirection.Buy ? quoteAsset
            : orderDirection == OrderDirection.Sell ? baseAsset
            : throw new InvalidOperationException();

        usedQuantities.TryGetValue(usedAsset, out var usedQty);
        var conversionRate = (orderDirection == OrderDirection.Buy) ? Securities[symbol].Price : 1.0m;
        usedQty += (orderTicket.Quantity - orderTicket.QuantityFilled) * conversionRate;
        usedQuantities[usedAsset] = usedQty;
    }

    // include unused assets
    foreach (var cash in Portfolio.CashBook.Keys)
        if (!usedQuantities.ContainsKey(cash))
            usedQuantities[cash] = 0m;

    return usedQuantities;
}

I think the API should provide a easy way to get this info.

Hey! Thanks for the report, believe it sounds similar to issue https://github.com/QuantConnect/Lean/issues/4987

Yes, it's similar. I'd like to have an API similar to CCXT which gives free, used and total quantities for each asset in the account.


⚠ Jenkins Plugins Artifactory has degraded performance

In b9dd9ea, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1406 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 99d39e8.


stream transform encoder and decoder

We converted the decoder and encoder into transform streams. This allows us to use them as input / output of a pipeline. Within the pipeline it is much easier to deal with the parsed data to monitor or modify it.

Looks like this works only with nodejs 0.12 and above.

I'm not really sure but your changes look like you need to change the unit tests in order to pass them.
And could you add 0.12 and 4.0 to the travis.yml?

Sure, updated the test cases and added one for testing the decoder/encoder pipeline. Also changed travis.yml to build for 0.12 and 4.0.

okay since this PR changes the API and dependencies, it should get a new major version number. 2.0.0 should be fine. I'll merge it later today (hopefully).

Thanks. Yes, a new major version number is certainly required.

merged, version updated & published. please test.
Thanks for the contribution!

Thanks, works perfect!


LAN server doesn't show up in clients unless net=host

Server seems to be starting ok but there's no way to connect to it from my android or ios devices. It doesn't show up in the "friends" tab at all.
If I set the docker to net=host then it works.
Docker arguments:
-e EULA=TRUE
--volume minecraft-data:/data
-e UID=1002
-e GID=1002
-p 19132:19132/udp
What's wrong?

Any news here?
I have the same problem. Minecraft server is running fine according to logs but on iOS nothing is shown. Restarted docker and Minecraft apps several times.