#bastion - March 2019 | Slack Archive

bastionArchived

54 messages

Discuss cloudposse/bastion

March 2019

Apr 2019

erikabout 7 years ago

@Erik Osterman (Cloud Posse) has joined the channel

erikabout 7 years ago

set the channel description: Discuss cloudposse/bastion

hairyhendersonabout 7 years ago

@hairyhenderson has joined the channel

hairyhendersonabout 7 years ago

w00t

Erik Osterman (Cloud Posse)about 7 years ago

What’s your challenge?

hairyhendersonabout 7 years ago

so I’m having a lot less trouble than I was 😉

hairyhendersonabout 7 years ago

the helm chart is… rusty 😉

Erik Osterman (Cloud Posse)about 7 years ago

Haha yes

Erik Osterman (Cloud Posse)about 7 years ago

We are using teleport with our customers now

hairyhendersonabout 7 years ago

oh really! 🤔

Erik Osterman (Cloud Posse)about 7 years ago

But we maybe able to address/fix problems in bastion

hairyhendersonabout 7 years ago

I’d looked at that, but bastion seems so much simpler 😉

Andriy Knysh (Cloud Posse)about 7 years ago

@Andriy Knysh (Cloud Posse) has joined the channel

Erik Osterman (Cloud Posse)about 7 years ago

Yes teleport is much more complicated, but also more feature rich

Erik Osterman (Cloud Posse)about 7 years ago

Bastion is quite simple by comparison

Erik Osterman (Cloud Posse)about 7 years ago

How far did you get and what’s the current problem?

hairyhendersonabout 7 years ago

sec - got pulled into a call 😬

Erik Osterman (Cloud Posse)about 7 years ago

No worries! Just post back here when you are free. I will also be jumping on a call shortly.

hairyhendersonabout 7 years ago

ok so… the initial problem was I was constantly getting Connection closed by authenticating user hairyhenderson 127.0.0.1 port 49698 [preauth] errors, and I couldn’t see github-authorized-keys being called, but it turns out the commented-out env vars in the values.yaml aren’t all the default values - specifically SSH_AUTHORIZED_KEYS_COMMAND: "/usr/bin/github-authorized-keys" is super-important to uncomment 😂

hairyhendersonabout 7 years ago

I’ll probably issue a PR with a bunch of updates once I’m through the learning curve 😉

Erik Osterman (Cloud Posse)about 7 years ago

Certainly - we'll get that approved quickly

Erik Osterman (Cloud Posse)about 7 years ago

ping me here, if you're blocked

Erik Osterman (Cloud Posse)about 7 years ago(edited)

the helm chart was a bit complicated as I recall due to the need for initializing a shared volume in /etc/ and running github-authorized-keys as a sidecar

erikabout 7 years ago

set the channel topic: https://github.com/cloudposse/bastion

Gonzalo Peciabout 7 years ago

@Gonzalo Peci has joined the channel

tamskyabout 7 years ago

@tamsky has joined the channel

Anmolabout 7 years ago

@Anmol has joined the channel

Juan Cruz Diazabout 7 years ago

@Juan Cruz Diaz has joined the channel

Leo Starcevicalmost 7 years ago

@Leo Starcevic has joined the channel

Leo Starcevicalmost 7 years ago(edited)

Hey guys!! Awesome work with the bastion container, but I have one issue, when building the image myself it won't run, I get


Initializing ssh-audit
- Enabling SSH Audit Logs
Password: chsh: PAM: Authentication token manipulation error
FATAL: Failed to initializeInitializing ssh-audit
- Enabling SSH Audit Logs
Password: chsh: PAM: Authentication token manipulation error
FATAL: Failed to initialize

Using the image from docker hub works fine though, any idea what could be wrong?