CHAMELEONSOCKS container restarts indefinitely

[kahteik]

After installing CHAMELEONSOCKS, external network is still unreachable. The status of the container is always "restarting (139)" according to docker ps. Tried to run docker logs chameleonsocks, but returned nothing at all.

This issue was not seen on Ubuntu.

Steps to reproduce the behavior:

1. Install docker from SWUPD.
   $ sudo https_proxy=https://myproxy.mycomp.com:<port> swupd bundle-add cloud-control
2. Reboot the system and log in to the desktop again.
3. Start docker service with this command
   $ sudo systemctl start docker
4. Run the following commands in the console for installation.
   $ sudo -s
$ https_proxy=https://myproxy.mycomp.com:<port> wget https://raw.githubusercontent.com/crops/chameleonsocks/master/chameleonsocks.sh && chmod 755 chameleonsocks.sh
$ https_proxy=https://myproxy.mycomp.com:<port> PROXY=mysocksproxy.mycomp.com PAC_URL=http://mysocksproxy.mycomp.com ./chameleonsocks.sh --install
5. Check container status
   $ sudo docker ps

Expected behavior
A container named chameleonsocks shall be seen with a status of "running".

Environment:

• Clear Linux OS version:
  NAME="Clear Linux OS"
  VERSION=1
  ID=clear-linux-os
  ID_LIKE=clear-linux-os
  VERSION_ID=29160
  PRETTY_NAME="Clear Linux OS"
  ANSI_COLOR="1;35"
  HOME_URL="https://clearlinux.org"
  SUPPORT_URL="https://clearlinux.org"
  BUG_REPORT_URL="mailto:dev@lists.clearlinux.org"
  PRIVACY_POLICY_URL="http://www.intel.com/privacy"
• Bundles:
  NetworkManager
  acpica-unix2
  alsa-utils
  baobab
  binutils
  bison
  bootloader
  c-basic
  cheese
  cloud-api
  cloud-control
  clr-network-troubleshooter
  curl
  desktop
  desktop-apps
  desktop-assets
  desktop-autostart
  desktop-gnomelibs
  desktop-locales
  diffutils
  dnf
  dpdk
  eog
  ethtool
  evince
  evolution
  file
  file-roller
  findutils
  firefox
  flatpak
  flex
  fonts-basic
  fuse
  gedit
  gimp
  git
  gjs
  glibc-locale
  gnome-base-libs
  gnome-calculator
  gnome-characters
  gnome-color-manager
  gnome-disk-utility
  gnome-font-viewer
  gnome-logs
  gnome-music
  gnome-photos
  gnome-screenshot
  gnome-system-monitor
  gnome-todo
  gnome-weather
  graphviz
  gstreamer
  gvim
  gzip
  hardware-printing
  htop
  iperf
  iproute2
  iptables
  kbd
  kernel-install
  kernel-lts
  kernel-lts2018
  kvm-host
  less
  lib-imageformat
  lib-opengl
  lib-openssl
  lib-samba
  libX11client
  libglib
  libstdcpp
  libva-utils
  linux-firmware
  linux-firmware-extras
  linux-firmware-wifi
  llvm
  locales
  make
  man-pages
  minicom
  nasm
  nautilus
  net-tools
  network-basic
  openblas
  openldap
  openssh-server
  openssl
  openvswitch
  os-core
  os-core-update
  os-core-webproxy
  p11-kit
  package-utils
  parallel
  patch
  perl-basic
  polkit
  powertop
  procps-ng
  pulseaudio
  pygobject
  python2-basic
  python3-basic
  seahorse
  sqlite
  strace
  sudo
  sysadmin-basic
  syslinux
  telemetrics
  thermal_daemon
  tmux
  totem
  tzdata
  unzip
  vim
  webkitgtk
  wget
  which
  wpa_supplicant
  x11-server
  xemacs
  xz
  znc
  zstd

[ahkok]

You wrote:

https_proxy=https://...

Make sure your proxy supports https. Most commonly, they do not, and you should instead write:

https_proxy=http://...

[kahteik]

You wrote:

https_proxy=https://...

Make sure your proxy supports https. Most commonly, they do not, and you should instead write:

https_proxy=http://...

The environment variables were defined correctly when I was running the command. In this bug description I just copied exactly from the instruction on its README.

[ahkok]

copied exactly from the instruction on its README.

The README does now know anything about your proxies. Some proxies support https, some do not.

This README is definitely incorrect for some proxy environments.

[ngaloppo]

Might be related: crops/chameleonsocks#9