# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 2032 # self = https://watcher.sour.is?uri=https://anthony.buc.ci/user/abucci/twtxt.txt&offset=1932 # prev = https://watcher.sour.is?uri=https://anthony.buc.ci/user/abucci/twtxt.txt&offset=1832
docker commands to podman syntax would work but it looks like it's more subtle than that. Thanks for trying!podman thought the connection was created, and it set it as the default. But I don't think it was sending anything over the wire. When I have more time to tinker with it maybe I'll play around and see if I can figure out what's up.
#!/bin/sh
set -e
alias docker=podman
if [ ! command -v docker > /dev/null 2>&1 ]; then
echo "docker not found"
exit 1
fi
mkdir -p $HOME/.docker/certs.d/cas
## key stuff omitted
# DO NOT DO THIS docker context create cas --docker "host=tcp://cas.run:2376,ca=$HOME/.docker/certs.d/cas/ca.pem,key=$HOME/.docker/certs.d/cas/key.pem,cert=$HOME/.docker/certs.d/cas/cert.pem"
# DO THIS:
podman system connection add "host=tcp://cas.run:2376,ca=$HOME/.docker/certs.d/cas/ca.pem,key=$HOME/.docker/certs.d/cas/key.pem,cert=$HOME/.docker/certs.d/cas/cert.pem"
# DO NOT DO THIS docker context use cas
# DO THIS:
podman system connection default cas
$ podman --docker
Error: unknown flag: --docker
podman doesn't have?
podman conforms to *some* of Docker's APIs and it's unclear to me which one you say it's *not* conforming to.podman works with TLS. It does not have the "--docker" siwtch so you have to remove that and use the exact replacement commands that were in that github comment.
podman can talk to the Docker Engine API. It's just that the commands sometimes have different names in the podmanverse. I think--never used those features.
dockerd is 96M and has to run all the time. You can't use docker without it running, so you have to count both. docker + dockerd is 131M, which is over 3x the size of podman. Plus you have this daemon running all the time, which eats system resources podman doesn't use, *and* docker fucks with your network configuration right on install, which podman doesn't do unless you tell it to.podman is free and open source software, the end. docker is a company with a pricing model. It was founded as a startup, which suggests to me that, like almost all startups, they are seeking an exit and if they ever face troubles in generating that exit they'll throw out all niceties and abuse their users (see Reddit, the drama with spyware in Audacity, 10,000 other examples). Sure you can use it free for many purposes, and the container bits are open source, but that doesn't change that it's always been a corporate entity, that they can change their policies at any time, that they can spy on you if they want, etc etc etc.podman is definitely capable of it. I've never used those features though so I'd have to play around with it awhile to understand how it works and then maybe I'd have a better idea of whether it's possible to get it to work with cas.run. podman-specific way of allowing remote container execution that wouldn't be too hard to support alongside docker if you wanted to go that route. Personally I don't use docker--too fat, too corporate. podman is lightweight and does virtually everything I'd want to use docker to do.
podman issue for adding the context subcommand that docker has. Currently podman does not have this subcommand, although this comment has a translation to podman commands that are similar-ish.cas.run add returns, changing all the docker commands to podman commands. Specifically, I put alias docker=podman at the top so the check for docker would pass, and then I replaced the last two lines of the script with these:
podman system connection add cas "host=tcp://cas.run..."
podman system connection default cas
cas.run is a bunch of connection-specific stuff)podman and I *think* they are running remotely but I don't know the right juju to verify. It looks right though!podman. Maybe when the check for docker fails, check for podman, and then later in the script use the podman equivalents to the docker context commands.
podman issue for adding the context subcommand that docker has. Currently podman does not have this subcommand, although this comment has a translation to podman commands that are similar-ish.cas.run add returns, changing all the docker commands to podman commands. Specifically, I put alias docker=podman at the top so the check for docker would pass, and then I replaced the last two lines of the script with these:
podman system connection add cas "host=tcp://cas.run..."
podman system connection default cas
cas.run is a bunch of connection-specific stuff)podman works but I believe that's what you need to do to get podman to run containers remotely.podman and I *think* they are running remotely but I don't know the right juju to verify. It looks right though!podman. Maybe when the check for docker fails, check for podman, and then later in the script use the podman equivalents to the docker context commands.
podman issue for adding the context subcommand that docker has. Currently podman does not have this subcommand, although this comment has a translation to podman commands that are similar-ish.podman right now! Details follow.cas.run add returns, changing all the docker commands to podman commands. Specifically, I put alias docker=podman at the top so the check for docker would pass, and then I replaced the last two lines of the script with these:
podman system connection add cas "host=tcp://cas.run..."
podman system connection default cas
cas.run is a bunch of connection-specific stuff)podman works but I believe that's what you need to do to get podman to run containers remotely.podman and I *think* they are running remotely but I don't know the right juju to verify. It looks right though!podman. Maybe when the check for docker fails, check for podman, and then later in the script use the podman equivalents to the docker context commands.
podman issue for adding the context subcommand that docker has. Currently podman does not have this subcommand, although this comment has a translation to podman commands that are similar-ish.podman right now! Though I'm not 100% sure the containers I tried really are running remotely. Details below.cas.run add returns, changing all the docker commands to podman commands. Specifically, I put alias docker=podman at the top so the check for docker would pass, and then I replaced the last two lines of the script with these:
podman system connection add cas "host=tcp://cas.run..."
podman system connection default cas
cas.run is a bunch of connection-specific stuff)podman works but I believe that's what you need to do to get podman to run containers remotely.podman and I *think* they are running remotely but I don't know the right juju to verify. It looks right though!podman. Maybe when the check for docker fails, check for podman, and then later in the script use the podman equivalents to the docker context commands.
$ ssh -p 2222 -i PRIVATE_GITHUB_KEY GITHUB_USERNAME@cas.run add | sh
sh: 135: docker: not found
## Quick Start
ssh -p 2222 cas.run add | sh
docker on this machine. Sorry about that, false alarm.
$ ssh -p 2222 -i PRIVATE_GITHUB_KEY GITHUB_USERNAME@cas.run add | sh
sh: 135: docker: not found
## Quick Start
ssh -p 2222 cas.run add | sh
$ ssh -p 2222 -i PRIVATE_GITHUB_KEY GITHUB_USERNAME@cas.run add | sh
sh: 135: docker: not found
## Quick Start
ssh -p 2222 cas.run add | sh
docker on this machine. Sorry about that.
ssh -p 2222 -i PRIVATE_GITHUB_KEY GITHUB_USERNAME@cas.run help
ssh and I haven't configured it to magically choose the key so I have to specify it in the command line.
ssh -p 2222 GITHUB_USERNAME@cas.run help but that gives the same error. There's something missing here.
ssh command you posted verbatim!
# ssh -p 2222 cas.run help
The authenticity of host '[cas.run]:2222 ([139.180.180.214]:2222)' can't be established.
RSA key fingerprint is SHA256:i5txciMMbXu2fbB4w/vnElNSpasFcPP9fBp52+Avdbg.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[cas.run]:2222' (RSA) to the list of known hosts.
abucci@cas.run: Permission denied (publickey).
jq after five years. This RC looks nice!
snac/the fediverse for a few days and already I've had to mute somebody. I know I come on strongly with my opinions sometimes and some people don't like that, but this person had already started going ad hominem (in my reading of it), and was using what felt to me like sketchy tactics to distract from the point I was trying to make and to shut down conversation. They were doing similar things to other people in the thread so rather than wait for it to get bad for me I just muted them. People get so weirdly defensive so fast when you disagree with something they said online. Not sure I fully understand that.
|
|
| .
| | |
| | |
| | |
|__________ | |
/ | _,..----. | / ,Y-o..
.| ,-'' | / .' / ' .
|| [ --.....- | | | `.
|| |".........__ | | \\ |
b | ' | | \\ |
| | | `. _,'
| | ' `'''
, , . .
\\ .'| ,-'\\V d---. |...
\\. ,'| / |/ | / |
` ...,' ,' `..,Y / / |
_/ | | |
,' |
-._______/
snac2, which I think @stigatle mentioned on here, and I have to say it's extremely easy to set up and it's been pretty straightforward so far. I wanted to experiment with having a presence on the Fediverse without going through the process of picking Mastodon vs. Gnu Social vs. Friendica vs. ..., and I wanted to self-host instead of picking an instance of one of those. For now I'm abucci@buc.ci, but no guarantees that will remain stable; I'm just testing for the time being.
snac2, which I think @stigatle mentioned on here, and I have to say it's extremely easy to set up and it's been pretty straightforward so far. I wanted to experiment with having a presence on the Fediverse without going through the process of picking a Mastdon vs. Gnu Social vs. Friendica vs. ..., and I wanted to self-host instead of picking an instance of one of those. For now I'm abucci@buc.ci, but no guarantees that will remain stable; I'm just testing for the time being.
fail2ban on very aggressive settings to avoid these headaches. That plus manually banning IP ranges that register bots on my pod (🙄) works pretty well for me.