failed to start [/usr/sbin/iptables-restore --wait 30 --wait-interval 100000]: exit status 2: unknown #34

Activity

1. wollomatic commented on Sep 21, 2024

   

   wollomatic

   on Sep 21, 2024

   Owner

   More actions

   I'm not familiar with sysbox-runc. Socket-proxy is just a SCRATCH image, so there is no /usr/sbin/iptables-restore binary in the container image. There is also no glibc or musl in the image that could be needed to run iptables-restore.

   Maybe it's worth a try to create a container image based on a distroless or a minimal linux image, like gcr.io/distroless/base-debian12:nonroot, alpine:3.20, or even Ubuntu.

   Sample Dockerfile:

   FROM wollomatic/socket-proxy:1 AS proxy
   FROM gcr.io/distroless/base-debian12:nonroot AS base
   VOLUME /var/run/docker.sock
   EXPOSE 2375
   ENTRYPOINT ["/socket-proxy"]
   COPY --from=proxy ./healthcheck ./socket-proxy /
   
2. johnwmail commented on Sep 22, 2024

   

   johnwmail

   on Sep 22, 2024

   Author

   More actions

   Thank for your sharing, thanks.

   I noticed, it works if comment out "#internal: true" (it also work, if external: false), thanks
   

   👍React with 👍1Reacted by Wolfgang Ellsässer
3. johnwmail

   closed this as completedon Sep 22, 2024
4. Repository owner locked and limited conversation to collaborators on Sep 22, 2024
5. wollomatic

   converted this issue into a discussion #37 on Sep 22, 2024