arm32v5/spiped
Spiped is a utility for creating symmetrically encrypted and authenticated pipes between sockets.
10K+
Note: this is the "per-architecture" repository for the arm32v5
builds of the spiped
official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.
Maintained by:
Tim Düsterhus (of the Docker Community), with Colin's support (from spiped upstream)
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile
linksWhere to file issues:
https://github.com/TimWolla/docker-spiped/issues
Supported architectures: (more info)amd64
, arm32v5
, arm32v6
, arm32v7
, arm64v8
, i386
, mips64le
, ppc64le
, riscv64
, s390x
Published image artifact details:
repo-info repo's repos/spiped/
directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/spiped
label
official-images repo's library/spiped
file (history)
Source of this description:
docs repo's spiped/
directory (history)
Spiped (pronounced "ess-pipe-dee") is a utility for creating symmetrically encrypted and authenticated pipes between socket addresses, so that one may connect to one address (e.g., a UNIX socket on localhost) and transparently have a connection established to another address (e.g., a UNIX socket on a different system). This is similar to ssh -L
functionality, but does not use SSH and requires a pre-shared symmetric key.
This image automatically takes the key from the /spiped/key
file (-k
) and runs spiped in foreground (-F
). Other than that it takes the same options spiped itself does. You can list the available flags by running the image without arguments:
$ docker run -it --rm arm32v5/spiped
usage: spiped {-e | -d} -s <source socket> -t <target socket> -k <key file>
[-DFj] [-f | -g] [-n <max # connections>] [-o <connection timeout>]
[-p <pidfile>] [-r <rtime> | -R]
For example running spiped to take encrypted connections on port 8025 and forward them to port 25 on localhost would look like this:
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 8025:8025 --init arm32v5/spiped -d -s '[0.0.0.0]:8025' -t '[127.0.0.1]:25'
Usually you would combine this image with another linked container. The following example would take encrypted connections on port 9200 and forward them to port 9200 in the container with the name elasticsearch
:
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 9200:9200 --link elasticsearch:elasticsearch --init arm32v5/spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
If you don't need any to bind to a privileged port you can pass --user spiped
to make spiped run as an unprivileged user:
$ docker run -d -v /path/to/keyfile:/spiped/key:ro --user spiped -p 9200:9200 --link elasticsearch:elasticsearch --init arm32v5/spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
You can save a new keyfile named spiped-keyfile
to the folder /path/to/keyfile/
by running:
$ docker run -it --rm -v /path/to/keyfile:/spiped/key arm32v5/spiped spiped-generate-key.sh
Afterwards transmit spiped-keyfile
securely to another host (e.g. by using scp).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository's spiped/
directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
docker pull arm32v5/spiped