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

Bitbucket Private Repository #31

Closed
dylansm opened this issue Nov 21, 2017 · 3 comments
Closed

Bitbucket Private Repository #31

dylansm opened this issue Nov 21, 2017 · 3 comments

Comments

@dylansm
Copy link

dylansm commented Nov 21, 2017

I'm trying to use a private repository hosted on Bitbucket and I can't get it to work using either auth.json or COMPOSER_AUTH environment variable. Either way I get a permission denied (publickey) error.

I'm following the directions here: https://getcomposer.org/doc/05-repositories.md#bitbucket-driver-configuration

I can confirm that I have a env variable COMPOSER_AUTH in my container and it looks like:

COMPOSER_AUTH={
  "bitbucket-oauth": {
    "bitbucket.org": {
      "consumer-key": "my-key",
      "consumer-secret": "my-secret"
    }
  }
}

Any thoughts on what I could try next? The only luck I've had is when I link my private key as a volume (but I don't want to use that method). Is there something I am missing? Some way to let docker composer know not to use a key but instead use OAuth?

@dylansm dylansm closed this as completed Nov 22, 2017
@dylansm
Copy link
Author

dylansm commented Nov 22, 2017

I'm closing this because it works if I properly link auth.json to /tmp/auth.json within container - using uid 1000 without home directory.

@alcohol
Copy link
Member

alcohol commented Nov 23, 2017

/tmp is the value of COMPOSER_HOME within the container.

Curious why the COMPOSER_AUTH approach did not work though.

@ItsReddi
Copy link

ItsReddi commented Dec 5, 2017

Could you please reopen this?
You have solved your problem in another way but the fact that COMPOSER_AUTH env variable does not work is still true

thank you :)

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

3 participants