Welcome to Nick's Random Musings

(Duplicated from Soldiersdisease.com when it went down).

Damion Romero DJ’ing on KXLU Los Angeles

Air Check Here

1. c11 439 – 1972.09.23 – (toshiba records – toct-8731)
2. high country steam – #484 2-8-2 great freight ’79 in thunderstorm – (arkay – ar-1058)
3. all steamed up! – #5506 burlington 2-8-2 – (howard fogg recordings)
4. twilight of steam – #15 2-8-2 – (mobile fidelity – mf 13)
5. steam echoes – u.p. #4005 “big boy” – (award high fidelity – e.p. ripley)
6. sunday only – #5632 4-8-4 – (mobile fidelity – mf 9)
7. steam railroading under thundering skies – #300 mikado 2-8-2 – (mobile fidelity – mf 8 )
8. hear that whistle blow – #25 2-6-2 & #19 2-8-2 doubleheader to pondosa – (mobile fidelity – mf 12)
9. ghost train – special whistle effect, grand trunk western #6323 4-8-4 – (mobile fidelity – mf 10)
10. steel rails under thundering skies – extra 1702 east with rear helper engine #11 – (bainbridge records – bt 6243)
11. whistling thru dixie – buffalo creek & gauley #4, 2-8-0 dundon to widen, west virginia, summer 1960 – (mobile fidelity – mf 6)
12. whistles west – s.p. 4436 northern 4-8-4 – (railway & locomotive historical society inc. – r-1319)
13. remember when? – aboard southern pacific’s starlight with daylight type 4460 – (mobile fidelity – mf 5/m)
14. the fading giant (sounds of steam railroading vol. 2) – train 42, the pelican, arrives rural retreat, va. with background of chimes from the lutheran church – departs. – (o. winston link)
15. highball – mainline 2- (mobile fidelity – mf 4)
16. freight service only – denver & rio grande western 488, 493 & 494 (2-8-2’s) – (s.k. railroad recordings – sk-103)
17. steam in colorado – freight extra, northbound for fort collins, with colorado & southern’s 282, #804, leaves boulder yard limits at 1:30 a.m. and works up a ruling grade, a mile from the microphone. – (mobile fidelity – trains#2)
18. great moments in steam railroading – side 2, track 1 – (mobile fidelity – trains#3)
19. berkshire in the alleghenies – scranton grade (on train) – (pilot to tender record co – pc 109)
20. the pennsylvania railroad – horseshoe curve spectacular – (semaphore – dlp-6001)

If docker is complaining about containers that cannot bind to ports, and you do not have other processes running on those ports, it may be that systemd has a bad ExecStart for docker, and it broke sub-process access.

It could look like: exec: “docker-proxy”: executable file not found in $PATH

Or is could be: level=debug msg=”FIXME: Got an API for which error does not match any expected type!!!: driver failed programming external connectivity on endpoint my-funny-valentine (43dc047fd585ce93dc8230d0ab60a8dfd3c5bef77b4055d218ed6722b416fd1d): Bind for 0.0.0.0:9092 failed: port is already allocated” error_type=types.internal module=api

Change this: systemd/system/docker.service.d/hosts.conf 2:ExecStart= 3:ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2736

To this: override.conf [Service] ExecStart= ExecStart=/usr/bin/dockerd [ngully@magpie docker.service.d]$ pwd /etc/systemd/system/docker.service.d

This was on Fedora 31, docker “moby-engine”

A whale of a good time.

If you are playing with docker, and want to mount a folder in your home directory, but end up getting your home directory instead, you might have misspelled it.

/home/ngully/experiment

vs.

/home/ngully/experement

And that’s the more you know.

Sent from my iPhone