-
Notifications
You must be signed in to change notification settings - Fork 178
Pushing the Docker image using FMP gives access denied #4
Comments
@arun-gupta Help me with some env config so I can replicate this? Seeing:
|
Seems like you don't have Docker running in your environment? Make sure Docker is running using one of the methods explained at https://store.docker.com/search?type=edition&offering=community. This is how FMP identifies the Docker host. |
@arun-gupta Nevermind; had just resetup Docker and forgot to add the group and permissions so I don't need to run as
Investigating; thanks. |
Charting further progressing and now at the point where I've replicated Arun's same error:
What's required is running the steps 1) and 2) under Docker Images here: https://github.com/aws-samples/aws-compute-options and then running |
@arun-gupta So I'm understanding the problem correctly, wouldn't I expect access denied here because I should instead be pushing to I'm currently not seeing the option to specify the namespace in https://maven.fabric8.io/#fabric8:push; does this correctly summarize the root cause, do you believe? |
Hm, even when changing
|
OK, @arun-gupta : I got this passing by first Is this a valid workaround for you to use FMP - assuming you |
Thanks for diving into this @ALRubinger, really appreciated |
It is absolutely a valid workaround, as long as it works in my setup. Here are the commands issued in my terminal:
As you can see, What could be the discrepancy in my setup? How should I further debug it? |
@arun-gupta I don't see where you issued Also this differs from the command I used by passing I can look again on my machine in a few hours, but yeah, |
@arun-gupta Yeah, check my traces below. First I am not logged into docker locally:
Then I attempt the same command you've provided me, which fails with familiar "requested access to the resource is denied" error:
Then I run
Finally I try the same command again and the pushes go forward:
|
@arun-gupta Note that my environment is Fedora:
@kenfinnigan notes that he's on Mac and sees the same issue you do; FMP doesn't seem to be respecting the login creds on that platform. We're looking into it. |
So the contents of my:
@kenfinnigan version has a |
The fix I believe, based on a naked-eye view, is in the
This does not support the keychain stuff used by Mac. Credentials on Linux are simply stored as a Base64 encoded String of form |
Some workarounds as per https://dmp.fabric8.io/#authentication
|
Underlying issue is here: fabric8io/docker-maven-plugin#946 @kenfinnigan to note a workaround for how to pass the username/password into the |
Added
|
Not sure why the system properties aren't working, as it's in the docs. Apologies though as I didn't directly try those settings. However, I did have success with I was looking for alternatives that didn't require password on command line |
Even
|
I didn't try running it with just the password. But if I pass the username and password that way, then it worked for me |
I added the following properties to
So, If both
These are the same values that are used with |
That's very weird, didn't have the same issue myself |
Closing this, following up at amazon-archives/microservices-greeting#3 |
Closing this, following up at amazon-archives/microservices-greeting#3 |
Pushing the Docker image using FMP gives the following error:
Pushing the image using Docker CLI works fine.
The text was updated successfully, but these errors were encountered: