alpine-docker / socat Goto Github PK

socat 1.7.4.1-r0 is available on the Alpine package tracker. Would PRs to update the version in the image be acceptable?

The current image is about a year old. Would it be possible to rebuild and push with an up-to-date Alpine base and socat version?

Hi Team,

I am working on enabling arm64 testing support in the consul repository. It uses this image to test envoy tests. Currently, the Socat image is not available for arm64. I have successfully built and tested the arm64 image with the below changes.

Commit: odidev@df5626f

It will be very helpful for arm64 users if the Socat image is released for arm64.

If the above changes looks good, I will raise a PR.

kubectl run auth-db-tunnel -it --image=alpine/socat --tty --rm --expose=true --port=5432 tcp-listen:5432,fork,reuseaddr tcp-connect:<aws_rds_host>:5432

service/auth-db-tunnel created
pod "auth-db-tunnel" deleted
service "auth-db-tunnel" deleted
error: timed out waiting for the condition

I would like to utilize this docker image on ARM devices (linux/arm/v7 to be precise). However, this image only supports linux/amd64:
$ docker run --rm mplatform/mquery alpine/socat
Image: alpine/socat
* Manifest List: No
* Supports: amd64/linux

Is it possible to build and publish multi-arch image (with manifest) similar to the official main alpine image?

Thank you.

I was attempting to set up a docker container to listen on a given port and to simply drop everything into a hole.

You can't use /dev/null, but - works. Outside docker, you can just:

socat -u - tcp-listen:2003,fork,reuseaddr

However, if you try this with the alpine/socat container, socat keeps closing the socket. It turns out that docker run needs -it, and that docker-compose.yml needs tty: true.

I think this'd make another good example use case, and the need for the TTY could be stated explicitly.

(it would have saved me a couple of hours this afternoon...)

The current image, 1.7.4.3-r1, was built 2 months ago, and today there are some known vulnerabilities in its dependencies.

If I rebuild the image today, with alpine:3.16.2 as base image, the resulting image does not have these vulnerabilities.

Is it possible to trigger Travis CI so a new image is pushed to hub.docker.com, even though there is no new tag of socat?

Thanks for providing this image!

Hi Team,

• I am using "alpine/socat:1.0.3" image for dockerd-exporter
• Passing args to image like.... args = ["IN=172.18.0.1:9323", "OUT=9323"]
• Then it's not running and got error

(ns: sshd) linuxkit-067f401a712e:/# docker service logs dockerd-exporter
dockerd-exporter.0.waae5pji8ptl@linuxkit-067f401a712e    | 2018/10/17 11:09:37 socat[1] E unknown device/address "IN=172.18.0.1"
dockerd-exporter.0.qqdc8zml9q6d@linuxkit-067f401a712e    | 2018/10/17 11:10:13 socat[1] E unknown device/address "IN=172.18.0.1"
dockerd-exporter.0.xw2pwg0gu090@linuxkit-067f401a712e    | 2018/10/17 11:10:06 socat[1] E unknown device/address "IN=172.18.0.1"
dockerd-exporter.0.gnuysmu12rvn@linuxkit-067f401a712e    | 2018/10/17 11:09:29 socat[1] E unknown device/address "IN=172.18.0.1"
dockerd-exporter.0.htk5ymrmwpb9@linuxkit-067f401a712e    | 2018/10/17 11:09:52 socat[1] E unknown device/address "IN=172.18.0.1"

(ns: sshd) linuxkit-067f401a712e:/# ifconfig | head -n20
docker0   Link encap:Ethernet  HWaddr 02:42:85:3B:5E:C0
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

docker_gwbridge Link encap:Ethernet  HWaddr 02:42:CF:75:9C:27
          inet addr:172.18.0.1  Bcast:172.18.255.255  Mask:255.255.0.0
          inet6 addr: fe80::42:cfff:fe75:9c27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35516 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40550 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:24627466 (23.4 MiB)  TX bytes:15982028 (15.2 MiB)

eth0      Link encap:Ethernet  HWaddr 06:7F:40:1A:71:2E
          inet addr:10.85.0.185  Bcast:10.85.0.255  Mask:255.255.255.128
          inet6 addr: fe80::2cfd:4543:9c13:a3d2/64 Scope:Link

I tired with ( 172.18.0.1, localhost, 127.0.0.1 and 172.17.0.1) but no luck still getting same error logs.
Any idea.?

Unfortunately it's not clear to me what exactly is broken. We use this image in CI, and the 1.7.4.0-r0 tag appears to not cat everything. Our tests are grepping the output for some lines, and as soon as this new image started being used the lines were missing.

Sorry I can't provide much more information, but I thought it may be helpful to someone.

We'll be pinning to one of the previous images for now. Reverting to the previous image makes the test pass again.

Using socat for host.docker.internal works with 1.7.3.4-r0.

# start container
docker run --rm -p8080:8080 alpine/socat:1.7.3.4-r1 'TCP-LISTEN:8080,fork', 'TCP:host.docker.internal:8080'

# call it
curl localhost:8080

# log
socat[6] E getaddrinfo("host.docker.internal", "NULL", {1,0,1,6}, {}): Name does not resolve