From charlesreid1

(Created page with "Each time I try and replicate this pipeline, a different piece goes wrong. This time, it's been the rsync stunnel container's secure communications port, 273, not opening up.")
 
No edit summary
Line 1: Line 1:
Each time I try and replicate this pipeline, a different piece goes wrong. This time, it's been the rsync stunnel container's secure communications port, 273, not opening up.
Current status: FIXING STUNNEL CONTAINER.
* Each time I try and replicate this pipeline, a different piece goes wrong.
* This time, it's been the rsync stunnel container's secure communications port, 273, not opening up between host/container.
* This is why we need Docker - *so* much bullshit involved in configuring Linux networking services. I'm not calling technical complexity bullshit, I'm calling hypernuanced, undocumented, impossible-to-debug network configuration and hardware issues bullshit.

Revision as of 18:44, 8 April 2017

Current status: FIXING STUNNEL CONTAINER.

  • Each time I try and replicate this pipeline, a different piece goes wrong.
  • This time, it's been the rsync stunnel container's secure communications port, 273, not opening up between host/container.
  • This is why we need Docker - *so* much bullshit involved in configuring Linux networking services. I'm not calling technical complexity bullshit, I'm calling hypernuanced, undocumented, impossible-to-debug network configuration and hardware issues bullshit.