toolshed/organising
toolshed/organising
7
1
Fork 0
Code Issues 127 Pull Requests Releases Activity

Setting up abra for the first time #641

New Issue
Closed
opened 2024-10-09 12:42:33 +00:00 by dphiffer · 4 comments
dphiffer commented 2024-10-09 12:42:33 +00:00
Copy Link

I'm still learning how all of this works and so far it's very impressive! Apologies if I'm missing an obvious detail. While going through the New Operator Tutorial I got stuck on the step for adding a new server:

$ abra server add social.coop       
INFO[0000] successfully created /Users/dphiffer/.abra/servers/social.coop 
INFO[0000] attempting to create client for social.coop  
INFO[0180] cleaning up context for social.coop          
INFO[0180] attempting to clean up server directory for social.coop 
FATA[0180] error during connect: Get "http://docker.example.com/v1.24/info": command [ssh -o ConnectTimeout=60 -l dphiffer -p 22 -- social.coop docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: connect to host hypha.social.coop port 22: Oper tion timed out

For reference, here is what I have in my .ssh/config, the port 22 part of the error looks like a likely culprit:

Host social.coop
  Hostname hypha.social.coop
  User dphiffer
  Port 2022
  IdentityFile ~/.ssh/lizano

And I did double check that I can ssh into the server:

$ ssh social.coop "lsb_release -a"
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy
No LSB modules are available.

I'm doing all of this from macOS 15.0.1 (24A348) running OpenSSH_9.8p1, LibreSSL 3.3.6.

I'm still learning how all of this works and so far it's very impressive! Apologies if I'm missing an obvious detail. While going through the [New Operator Tutorial](https://docs.coopcloud.tech/operators/tutorial/) I got stuck on the step for adding a new server: ``` $ abra server add social.coop INFO[0000] successfully created /Users/dphiffer/.abra/servers/social.coop INFO[0000] attempting to create client for social.coop INFO[0180] cleaning up context for social.coop INFO[0180] attempting to clean up server directory for social.coop FATA[0180] error during connect: Get "http://docker.example.com/v1.24/info": command [ssh -o ConnectTimeout=60 -l dphiffer -p 22 -- social.coop docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: connect to host hypha.social.coop port 22: Oper tion timed out ``` For reference, here is what I have in my `.ssh/config`, the port 22 part of the error looks like a likely culprit: ``` Host social.coop Hostname hypha.social.coop User dphiffer Port 2022 IdentityFile ~/.ssh/lizano ``` And I did double check that I can ssh into the server: ``` $ ssh social.coop "lsb_release -a" Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy No LSB modules are available. ``` I'm doing all of this from macOS 15.0.1 (24A348) running OpenSSH_9.8p1, LibreSSL 3.3.6.
❤️ 1
decentral1se commented 2024-10-10 10:01:07 +00:00
Owner
Copy Link

@dphiffer thanks for the kind words!

We've reworked how SSH connection details are implemented in the latest unreleased version of abra so as to avoid problems like this going forward. Sorry for this blocker...

In the stack, I see "connect to host hypha.social.coop port 22: Operation timed out". So, it seems somehow, abra is somehow turning social.coop on the command-line to hypha.social.coop on the lookup in ~/.ssh/config.

I would probably hack something together like:

Host hypha.social.coop
  Hostname hypha.social.coop
  User dphiffer
  Port 2022
  IdentityFile ~/.ssh/lizano

Or even maybe Host social.coop hypha.social.coop.

Sharing any --debug output would be appreciated.

But yeh, we're removed most of this logic and rely on SSH itself to resolve this stuff going forward. Hopefully a release is forthcoming in the near future!

Lemme know if you get further with this and thanks for the patience!

@dphiffer thanks for the kind words! We've reworked how SSH connection details are implemented in the latest unreleased version of `abra` so as to avoid problems like this going forward. Sorry for this blocker... In the stack, I see "connect to host hypha.social.coop port 22: Operation timed out". So, it seems somehow, `abra` is somehow turning `social.coop` on the command-line to ` hypha.social.coop` on the lookup in `~/.ssh/config`. I would probably hack something together like: ``` Host hypha.social.coop Hostname hypha.social.coop User dphiffer Port 2022 IdentityFile ~/.ssh/lizano ``` Or even maybe `Host social.coop hypha.social.coop`. Sharing any `--debug` output would be appreciated. But yeh, we're removed most of this logic and rely on SSH itself to resolve this stuff going forward. Hopefully a release is forthcoming in the near future! Lemme know if you get further with this and thanks for the patience!
dphiffer commented 2024-10-23 12:14:49 +00:00
Author
Copy Link

Thanks for the response, and sorry for the slow reply.

I updated my .ssh/config to match your suggestion:

Host social.coop hypha.social.coop
  Hostname hypha.social.coop
  User dphiffer
  Port 2022
  IdentityFile ~/.ssh/lizano

Here's what I see now:

$ abra server add hypha.social.coop --debug
DEBU[0000] validated hypha.social.coop as domain argument  caller="/drone/src/cli/internal/validate.go:116 ValidateDomain"
INFO[0000] successfully created /Users/dphiffer/.abra/servers/hypha.social.coop  caller="/drone/src/pkg/server/server.go:24 CreateServerDir"
DEBU[0000] retrieved ssh config for hypha.social.coop: {host: hypha.social.coop, username: dphiffer, port: 2022, identityfile: ~/.ssh/id_rsa}  caller="/drone/src/pkg/ssh/ssh.go:63 GetHostConfig"
DEBU[0000] creating context with domain hypha.social.coop, username dphiffer and port 2022  caller="/drone/src/cli/server/add.go:70 newContext"
DEBU[0000] created the hypha.social.coop context         caller="/drone/src/pkg/client/context.go:29 CreateContext"
INFO[0000] attempting to create client for hypha.social.coop  caller="/drone/src/cli/server/add.go:170 glob..func1"
DEBU[0000] created client for hypha.social.coop          caller="/drone/src/pkg/client/client.go:68 New"
DEBU[0000] commandconn: starting ssh with [-o ConnectTimeout=60 -l dphiffer -p 2022 -- hypha.social.coop docker system dial-stdio]  caller="/drone/src/pkg/upstream/commandconn/commandconn.go:49 New"
DEBU[0002] commandconn (ssh):failed to open the raw stream connection: dial unix /var/run/docker.sock: connect: permission denied  caller="/drone/src/pkg/upstream/commandconn/commandconn.go:287 (*stderrWriter).Write"
DEBU[0002] commandconn: starting ssh with [-o ConnectTimeout=60 -l dphiffer -p 2022 -- hypha.social.coop docker system dial-stdio]  caller="/drone/src/pkg/upstream/commandconn/commandconn.go:49 New"
DEBU[0004] commandconn (ssh):failed to open the raw stream connection: dial unix /var/run/docker.sock: connect: permission denied  caller="/drone/src/pkg/upstream/commandconn/commandconn.go:287 (*stderrWriter).Write"
INFO[0004] cleaning up context for hypha.social.coop     caller="/drone/src/cli/server/add.go:28 cleanUp"
INFO[0004] attempting to clean up server directory for hypha.social.coop  caller="/drone/src/cli/server/add.go:34 cleanUp"
DEBU[0004] failed to construct client for hypha.social.coop, saw Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running?  caller="/drone/src/cli/server/add.go:173 glob..func1"
FATA[0004] Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running?  caller="/drone/src/cli/server/add.go:174 glob..func1" stack="/drone/src/cli/server/add.go:174                         glob..func1\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524     HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405     (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277     (*App).Run\n/drone/src/cli/cli.go:203                                RunApp\n/drone/src/cmd/abra/main.go:22                           main\n/usr/local/go/src/runtime/internal/atomic/types.go:194   (*Uint32).Load\n/usr/local/go/src/runtime/asm_arm64.s:1197               goexit"

It's a new error, so progress! I have a suspicion that my user account on the server needs more privileges to work with the running Docker containers, but I'm not sure where to go from here.

Thanks for the response, and sorry for the slow reply. I updated my `.ssh/config` to match your suggestion: ``` Host social.coop hypha.social.coop Hostname hypha.social.coop User dphiffer Port 2022 IdentityFile ~/.ssh/lizano ``` Here's what I see now: ``` $ abra server add hypha.social.coop --debug DEBU[0000] validated hypha.social.coop as domain argument caller="/drone/src/cli/internal/validate.go:116 ValidateDomain" INFO[0000] successfully created /Users/dphiffer/.abra/servers/hypha.social.coop caller="/drone/src/pkg/server/server.go:24 CreateServerDir" DEBU[0000] retrieved ssh config for hypha.social.coop: {host: hypha.social.coop, username: dphiffer, port: 2022, identityfile: ~/.ssh/id_rsa} caller="/drone/src/pkg/ssh/ssh.go:63 GetHostConfig" DEBU[0000] creating context with domain hypha.social.coop, username dphiffer and port 2022 caller="/drone/src/cli/server/add.go:70 newContext" DEBU[0000] created the hypha.social.coop context caller="/drone/src/pkg/client/context.go:29 CreateContext" INFO[0000] attempting to create client for hypha.social.coop caller="/drone/src/cli/server/add.go:170 glob..func1" DEBU[0000] created client for hypha.social.coop caller="/drone/src/pkg/client/client.go:68 New" DEBU[0000] commandconn: starting ssh with [-o ConnectTimeout=60 -l dphiffer -p 2022 -- hypha.social.coop docker system dial-stdio] caller="/drone/src/pkg/upstream/commandconn/commandconn.go:49 New" DEBU[0002] commandconn (ssh):failed to open the raw stream connection: dial unix /var/run/docker.sock: connect: permission denied caller="/drone/src/pkg/upstream/commandconn/commandconn.go:287 (*stderrWriter).Write" DEBU[0002] commandconn: starting ssh with [-o ConnectTimeout=60 -l dphiffer -p 2022 -- hypha.social.coop docker system dial-stdio] caller="/drone/src/pkg/upstream/commandconn/commandconn.go:49 New" DEBU[0004] commandconn (ssh):failed to open the raw stream connection: dial unix /var/run/docker.sock: connect: permission denied caller="/drone/src/pkg/upstream/commandconn/commandconn.go:287 (*stderrWriter).Write" INFO[0004] cleaning up context for hypha.social.coop caller="/drone/src/cli/server/add.go:28 cleanUp" INFO[0004] attempting to clean up server directory for hypha.social.coop caller="/drone/src/cli/server/add.go:34 cleanUp" DEBU[0004] failed to construct client for hypha.social.coop, saw Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running? caller="/drone/src/cli/server/add.go:173 glob..func1" FATA[0004] Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running? caller="/drone/src/cli/server/add.go:174 glob..func1" stack="/drone/src/cli/server/add.go:174 glob..func1\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524 HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405 (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277 (*App).Run\n/drone/src/cli/cli.go:203 RunApp\n/drone/src/cmd/abra/main.go:22 main\n/usr/local/go/src/runtime/internal/atomic/types.go:194 (*Uint32).Load\n/usr/local/go/src/runtime/asm_arm64.s:1197 goexit" ``` It's a new error, so progress! I have a suspicion that my user account on the server needs more privileges to work with the running Docker containers, but I'm not sure where to go from here.
decentral1se commented 2024-10-23 16:31:33 +00:00
Owner
Copy Link

hey @dphiffer nice!

"I have a suspicion that my user account on the server needs more privileges to work with the running Docker containers"

yeh that "Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running?" is suspect.

on your server, if you run groups for your user, do you see docker? you can add the user with sudo usermod -aG docker <username> (think you have to log out and in again to effect changes).

Or just running docker ps as your user on the server and see what you get back?

hey @dphiffer nice! > "I have a suspicion that my user account on the server needs more privileges to work with the running Docker containers" yeh that "Cannot connect to the Docker daemon at http://docker.example.com. Is the docker daemon running?" is suspect. on your server, if you run `groups` for your user, do you see `docker`? you can add the user with `sudo usermod -aG docker <username>` (think you have to log out and in again to effect changes). Or just running `docker ps` as your user on the server and see what you get back?
👍 1
dphiffer commented 2024-10-30 12:22:55 +00:00
Author
Copy Link

Heyyy it works!

$ abra server add hypha.social.coop
INFO[0000] successfully created /Users/dphiffer/.abra/servers/hypha.social.coop 
INFO[0000] attempting to create client for hypha.social.coop 
INFO[0004] hypha.social.coop added

Thanks for guiding me through that @decentral1se, and for the assist on the server permissions side, @3wordchant.

Heyyy it works! ``` $ abra server add hypha.social.coop INFO[0000] successfully created /Users/dphiffer/.abra/servers/hypha.social.coop INFO[0000] attempting to create client for hypha.social.coop INFO[0004] hypha.social.coop added ``` Thanks for guiding me through that @decentral1se, and for the assist on the server permissions side, @3wordchant.
🎉 2
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
abra

Everything to do with abra

  
abra-gandi

Abra Gandi plugin

  
awaiting-feedback

Ping/pong on comms

  
backups

   
bug

Something is not working

  
build

Go build related issues

  
ci/cd

Getting the robots into the mix

  
community organising

Opening this thing up

  
contributing

Contributors stuff

  
coopcloud.tech

Our main website

  
democracy

Democratic decision making

  
design

Design thinking required

  
documentation

Let's write things together

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
finance

Money things

  
funding

Anything related to grant funding

  
good first issue

Easy start with development

  
help wanted

Need some help

  
installer

Installation related issues

  
kadabra

   
performance

Performance related

  
proposal

Large change which requires feedback & decisin making

  
question

More information is needed

  
recipes.coopcloud.tech

Our recipes catalogue

  
security

Securing our shit

  
test

Unit or integration test suite

  
wontfix

This won't be fixed

No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#641
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?