![Namecheap Takes Down Polyfill.io Service Following Supply Chain Attack](https://cdn.sanity.io/images/cgdhsj6q/production/6af25114feaaac7179b18127c83327568ff592d1-1024x1024.webp?w=800&fit=max&auto=format)
Security News
Namecheap Takes Down Polyfill.io Service Following Supply Chain Attack
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Readme
docker-tunnel
is a console utility to use remote docker with SSH tunnel.
If you are using OS X or a Linux distribution with docker-unsupported kernel, no more running a virtual machine or ssh to a remote shell.
With pip::
$ pip install docker-tunnel
With pipsi_ (Recommended)::
$ pipsi install docker-tunnel
::
$ docker-tunnel user@example.com
(user@example.com) $
(user@example.com) $ echo $DOCKER_HOST
127.0.0.1:4243
(user@example.com) $ docker ps # go ahead
...
(user@example.com) $ ^D # ctrl-d
$
More options::
$ docker-tunnel --help
Inside the tunnel injected shell, the environment variable DOCKER_HOST
and DOCKER_PROMPT_INFO
will be assigned. They can be used in your shell theme to prompt you which tunnel is using.
There is an example, my custom theme
_ for OH-MY-ZSH.
Error response from daemon: client and server don't have same version (client : 1.14, server: 1.12)
The docker in source of CentOS 7 is using API 1.12 but the docker client in Homebrew of OS X is not. You can downgrade the docker client with Homebrew::
$ brew versions docker
...
1.0.0 git checkout c513c42 /usr/local/Library/Formula/docker.rb
...
$ cd /usr/local/Library/Formula # now we install the old version of docker
$ git checkout c513c42 -- docker.rb
$ brew unlink docker
$ brew install docker
$ git checkout HEAD -- docker.rb
$ cd -
$ brew info docker # check the installed versions and current version
...
/usr/local/Cellar/docker/1.1.1 (9 files, 9.8M) *
Poured from bottle
/usr/local/Cellar/docker/1.2.0 (9 files, 6.6M)
Poured from bottle
...
$ docker-tunnel user@example.com
(user@example.com) $ docker version
Client version: 1.0.0
Client API version: 1.12
...
(user@example.com) $ exit
$ brew switch 1.2.0 # restore to latest
bind: Address already in use. cannot listen to port: 4243
You can find out the process which held the 4243
port with sudo lsof -i :4243
and decide to kill it or pick another port with --local-port
.
channel 1: open failed: connect failed: Connection refused. 2014/09/06 13:08:57 Get http://127.0.0.1:4243/v1.14/info: EOF
Does the docker server listen on 127.0.0.1:2375
? You may have to set correct server info with --remote-host
and --remote-port
.
If you want to report bugs or request features, please create issues on
GitHub Issues <https://github.com/tonyseek/docker-tunnel/issues>
_.
.. _pipsi: https://github.com/mitsuhiko/pipsi
.. _my custom theme
: https://github.com/tonyseek/oh-my-zsh-seeker-theme
.. |Wheel Status| image:: https://pypip.in/wheel/docker-tunnel/badge.svg :target: https://warehouse.python.org/project/docker-tunnel :alt: Wheel Status .. |PyPI Version| image:: https://img.shields.io/pypi/v/docker-tunnel.svg :target: https://pypi.python.org/pypi/docker-tunnel :alt: PyPI Version .. |PyPI Downloads| image:: https://img.shields.io/pypi/dm/docker-tunnel.svg :target: https://pypi.python.org/pypi/docker-tunnel :alt: Downloads
FAQs
Using remote docker with SSH tunnel.
We found that docker-tunnel demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.
Security News
A JavaScript library maintainer is under fire after merging a controversial PR to support legacy versions of Node.js.