I cant push docker images to packages containers

[Andres P]

I have send in the latest screenshots every possible scenario that i try and settings and scopes.

I have done:

1. make a new package to put the images name testcontainer

2. New API with all the 40+ scopes (previously tried with api key and this scopes:- `read:repository:bitbucket`
   - `write:repository:bitbucket`
   - `read:package:bitbucket`
   - `write:package:bitbucket`)

3. followed the packages section instructions:

4. The Bitbucket is connected to the workspace: companynameworkspace
5. The subscribtion plan is premium free trial. That Atlassian support told me could use for the docker testing.
6. My user has admin right to bitbucket and the workspace, actuallt to everything.
7. the login is succesful with my altasian account email and api key
8. The api key was created under https://id.atlassian.com/manage-profile/security/api-tokens.

---

       10. tried via bitbucket-pipelines.yml and from the terminal in my laptop. where in both case i have succesfully login in to the Bitbucket via username and api key with ALL the scopes enabled

       11. then in both pipeline and terminal:

docker build -t crg.apkg.io/companynameworkspace/testcontainer:latest .

docker push crg.apkg.io/companynameworkspace/testcontainer:latest

and both cases same error:

error from registry: You may not have access to this image or it does not exist in this workspace.

It cant be this difficult to work with pipelines with jira, in gitlab and github and yeah everywhere else is quite straight forward, i have just tried to push same  image to a new gitlab account and github and it took literally 5 minutes from i create each account and have everything working.

I hope we can solve this because we really want to give this a fair chance and have everything in only one place. Atlantis.

[Syahrul]

Hey @Andres P 

Welcome to the community.

I tested using my read/write packages API token and was able to push the package without any issues. If you'd like to investigate further, please raise a support ticket on our Support portal. This will enable us to investigate the matter further. 

Regards,
Syahrul