Bryan Kneis comments

Results 64 comments of


                                            Bryan Kneis

Reference local folder for --dotfiles option

@anibal-aguila thanks for reporting your use case, that does looks like it would be common. I'm surprised this fails though, I expected the config `SSH_INJECT_GIT_CREDENTIALS` to default to true here...

Reference local folder for --dotfiles option

@anibal-aguila thanks for that. Which provider are you using? The error seems to be `13:09:18 info ssh: Could not resolve hostname github.com: Name or service not known`. Can you check...

Adding AWS Provider throws fatal error "not found, exit status 127"

Hi @sowhatdoido can you add the aws binary to your PATH and try again?

Adding AWS Provider throws fatal error "not found, exit status 127"

@sowhatdoido Another user reported something similiar in https://github.com/loft-sh/devpod/issues/1250, could you try the fix there and see if that works for you? Simply wrap the call to DevPod Desktop in a...

Adding AWS Provider throws fatal error "not found, exit status 127"

Completely agree, that's why I left this open. I've been closing similar issues to reduce the number of duplicates, since the root cause is the same

Adding AWS Provider throws fatal error "not found, exit status 127"

No worries @sowhatdoido, I'm going to keep this open as I only wanted to test a workaround. The root cause is still an issue so will keep open until we...

Cannot forward gpg-agent with devpod in a "docker-in-docker" container

Hey @RishikesavanRamesh thanks for reporting your issue! Devpod uses a server under the hood running on port `12049` to forward the GPG keys from your local machine to the workspace....

git-remote-https: Undefined symbol: EVP_md2, version OPENSSL_3.0.0

thanks for reporting the issue @piellick, Does performing `git clone` on the repo you are using work?

"<external command>": executable file not found in $PATH, out: `` in the UI

replied already on https://github.com/loft-sh/devpod/issues/1155

Support devcontainers on Linux hosts using SELinux

Thanks @haakobja for reporting the issue and providing a good summary of the problem. I'm not too sure if we should change devpod though to accommodate this, other than document...