Anton Piatek on Nostr: npub198t8k…5hasj npub1nc7zs…sfpr5 npub10jld8…e5yg5 sorry, yes the restart was ...
npub198t8kgwqas59rvmnghzcdn6krzhxhpkyt2mt53e4g9sdnj74sszss5hasj (npub198t…hasj) npub1nc7zsjcqc3cyyxdgej82t9cl5uuqxvql8qul4jfwkca7dg76lsfsksfpr5 (npub1nc7…fpr5) npub10jld8lmu7tjn56lrl3cln0s6r794yk3t6fcp7q4h08m03ag2j98qke5yg5 (npub10jl…5yg5) sorry, yes the restart was just because I always forget about it and then wonder why several months later it isn't running, and I'd rebooted.
The -d flag should be enough to keep it running after ssh close. Are you sure it's not stopping for some other reason?
Docker runs as a daemon so -d doesn't run the process under your process tree so there should be nothing to kill when sssh closes (unless you have some unusual install?)
The -d flag should be enough to keep it running after ssh close. Are you sure it's not stopping for some other reason?
Docker runs as a daemon so -d doesn't run the process under your process tree so there should be nothing to kill when sssh closes (unless you have some unusual install?)