Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building and running Lacework CLI in Docker-less environments using podman and buildah #167

Open
marcredhat opened this issue Jul 19, 2020 · 1 comment

Comments

@marcredhat
Copy link

Hi,

Please find below how I build and run Lacework CLI containers in Docker-less environments using podman and buildah:

Buildah from scratch:
https://github.com/marcredhat/lacework/blob/master/demo4.sh

Buildah from Dockerfile:
https://github.com/marcredhat/lacework/blob/master/demo3.sh

Hope this helps,
Marc

@afiune
Copy link
Contributor

afiune commented Jul 20, 2020

Hey Marc, thank you for bringing these demos to our attention and to play with the Lacework CLI! 💯

I have a couple of things to mention, the first one is that we introduced a new feature to the
lacework configure command to run non-interactively. I saw that your shell scripts are executing
the command:

lacework configure --account "<account>" --api_key "<API key>" --api_secret "<API secret>"

I would recommend you to pass the flag --noninteractive to the previous command to avoid the
interactions with a prompt.

The second thing to mention is that we do have a certified container for our agent:

But, we do not have a container for our CLI, which is definitely a feature we would like to have and that you
have already contributed with your scripts. 🥇 Thank you for that!

Last, we were wondering what was the motivation to work on this? what are you using the Lacework CLI for?
Is there anything we can help you with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants