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

update README for revised docker compose instructions to reflect new docker container location #11

Closed
snicker opened this issue Nov 11, 2023 · 3 comments · Fixed by #12

Comments

@snicker
Copy link
Collaborator

snicker commented Nov 11, 2023

per #10 - v0.1.0 published
https://github.com/snicker/juicepassproxy/releases/tag/v0.1.0

@Snuffy2

I can then test to ensure it works and will then make another PR to update the Readme with revised Docker Compose instructions.

all yours!

@snicker snicker changed the title update README update README for revised docker compose instructions to reflect new docker container location Nov 11, 2023
@snicker
Copy link
Collaborator Author

snicker commented Nov 11, 2023

@Snuffy2 - this is failing, likely because I do not have a token defined in the secrets of the repository

Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/snicker/juicepassproxy:0.1.0: unexpected status from POST request to https://ghcr.io/v2/snicker/juicepassproxy/blobs/uploads/: 403 Forbidden

I tried setting up a fine grained access token for deployments, but I must be doing something wrong since GH will not allow me to include a personal access token in the repo secrets.

If you can give me some instructions on setting this part up I can implement this weekend.

@Snuffy2
Copy link
Collaborator

Snuffy2 commented Nov 11, 2023

Hopefully, we can fix it easily with the Repo permissions.

Go into the Repo, Settings, Actions, General.

Change the settings per below:
2023-11-11_13-52-11

Then try to rerun the Action.

Go into the Repo, Actions, Click the v0.1.0 run. Then click Re-run jobs and cross your fingers.

2023-11-11_13-55-45

@snicker
Copy link
Collaborator Author

snicker commented Nov 11, 2023

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

Successfully merging a pull request may close this issue.

2 participants