-
Notifications
You must be signed in to change notification settings - Fork 176
Authentication failed for 'https://github.com/EpicGames/UnrealEngine.git/' #290
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
Comments
I see that there is a |
Do not enter your GitHub password. Instead, enter GitHub access token with |
I am entering a token into the password field. I have confirmed that the
token works to clone the repository.
…On Sat, Dec 10, 2022, 11:14 AM Marat Radchenko ***@***.***> wrote:
Do not enter your GitHub password. Instead, enter GitHub access token with
repo scope.
—
Reply to this email directly, view it on GitHub
<#290 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDU3JTYCBEDNDFIMLXEVODWMTB65ANCNFSM6AAAAAAS2J5RYQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Okay, let's check one more thing. Are you using classic token (obtainable at https://github.com/settings/tokens/new)? You only need to add |
I'm out of ideas then. The only case when GitHub says "Support for password authentication was removed on August 13, 2021" I am aware of is when user tries to use password for authentication. |
I'm definitely not using my password. I'll try to find the place in the
code where the authentication request is happening and repeat the exact
authentication steps manually to try to get some clues.
…On Mon, Dec 12, 2022, 6:18 AM Marat Radchenko ***@***.***> wrote:
I'm out of ideas then. The only case when GitHub says "Support for
password authentication was removed on August 13, 2021" I am aware of is
when user tries to use *password* for authentication.
—
Reply to this email directly, view it on GitHub
<#290 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDU3JTP65NVSMFJXAOJH7DWM4Q2NANCNFSM6AAAAAAS2J5RYQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have determined that the build is getting to
I am not sure if this is expected behavior, or it should have entered the other if branch {% if credential_mode == "secrets" %} . I haven't yet been able to determine where the credential_mode is set or how to see the key values pairs in git_config.items() . Does this help at all?
|
Moreover, the ue4-docker/ue4docker/dockerfiles/ue4-source/linux/Dockerfile Lines 70 to 80 in 15cf89d
|
Is there some assumption built in about how credentials are being managed? I couldn't get it to go with the code that is there. With the following change to the Dockerfile I got it to go. It's easy to see how this approach could be made to work with command line argument substitutions.
|
It's not the ue4-docker/ue4docker/dockerfiles/ue4-source/linux/Dockerfile Lines 64 to 67 in 15cf89d
If the |
@wohlbier the approach depicted in your diff will leak your GitHub credentials into the image history, which is a security risk that ue4-docker goes to great lengths to avoid. Credentials are passed to git by means of a credential helper script, with separate helper script implementations for the two different credential modes: credential endpoint mode and BuildKit secrets mode. As @TBBle mentioned above, the helper script is configured using the The first question that needs to be answered is which credential mode (and thus which helper script) is being used, since the subsequent steps for debugging any problems will vary based on the specific implementation. If you run Here's an example of what the command looks like when using credential endpoint mode (note the presence of the
And here's an example of what the command looks like when using BuildKit secrets mode (note the presence of the two
Could you please paste the build command that ue4-docker prints for the |
Here's the output from that command with
|
@wohlbier okay, that narrows things down a bit. What happens if you specify |
@adamrehn that appears to be working ... I swore I had tried that already. |
@wohlbier okay, that suggests there's something about your system's network configuration that's interfering with the credential endpoint then (e.g. firewall rules, proxy settings, etc.) If you run the @slonopotamus @TBBle given that we always use BuildKit when building Linux containers these days, should we simply set secrets mode as the default credential mode for Linux containers? It provides better caching behaviour for rebuilds due to the absence of an ever-changing token, and it'd alleviate a number of firewall concerns that we currently have to worry about by default. |
Yeah, I think secrets mode should be the default, I hadn't realised we hadn't already made that change when making BuildKit required, since it's one of the big wins from BuildKit support. |
+1 from me. |
Additional thoughts: we've had BuildKit enabled on Linux for several months already and didn't get any negative feedback (well, except log truncation, but we can fix that via |
We could definitely configure this automatically, although it'll probably need to vary based on how different distros package the Docker daemon. Under Ubuntu, I edit
After editing the file, I restart the Docker Daemon by running the following systemd-specific commands:
|
resolves #290 use BuildKit secrets by default for Linux containers
Output of the
ue4-docker info
command:Additional details:
I'm using a token that I have verified allows me to clone https://github.com/EpicGames/UnrealEngine.git.
The text was updated successfully, but these errors were encountered: