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

Docker uplink-cli image run guide #109

Open
ValeriiLav opened this issue Aug 12, 2022 · 3 comments
Open

Docker uplink-cli image run guide #109

ValeriiLav opened this issue Aug 12, 2022 · 3 comments

Comments

@ValeriiLav
Copy link

ValeriiLav commented Aug 12, 2022

Hi there!
Is it possible to provide to community manual on how to run the uplink docker image?

When I run uplink in docker-compose

  uplink:
    container_name: Uplink
    image: docker.io/storjlabs/uplink:latest
    networks:
      - fullstack
    volumes:
      - /root/.config/storj/uplink:/root/.local/storj/uplink
    env_file:
      - .env      

with .env:

API_KEY=xxx
SATELLITE_ADDR=12xxx@eu1.storj.io:7777

configs in root/.config/storj/uplink:

~/.config/storj/uplink# cat access.json 
{
	"Default": "shellmetadatas_access_s3_api",
	"Accesses": {
		"shellmetadatas_access_s3_api": "xxx"
	}
} 

~/.config/storj/uplink# cat config.ini - empty

and instantly after start it throws error:

~#  docker logs Uplink
Error: uplink: API key cannot be empty
Select your satellite:
	[1] us1.storj.io
	[2] eu1.storj.io
	[3] ap1.storj.io
Enter number or satellite address as "<nodeid>@<address>:<port>" [1]: Choose an access name (use lowercase letters) ["default"]: Enter your API key: 
@Erikvv Erikvv changed the title Docker uplink image run guide Docker uplink-cli image run guide Aug 12, 2022
@Erikvv
Copy link
Contributor

Erikvv commented Aug 12, 2022

Thanks for your report.

This container has been unmaintained for a long time and the current version no longer works due to several bugs in the entrypoint. The Dockerfile was removed in the beginning of this year.

But I think it would be good to release a new working container again.

Can you describe to me what you are trying to achieve? I'd like to be sure it will actually help you. Are you trying to use uplink-cli?

@ValeriiLav
Copy link
Author

ValeriiLav commented Aug 15, 2022

Hello @Erikvv, thanks for the fast response.

I am going to run uplink as a microservice through docker-compose.
So that it would be nice to have an option to pass settings to docker container through .env file, or at least a confiing.json.

Can you describe to me what you are trying to achieve?

We need to share access to the files that are in the bucket. For each file, there will be a dedicated URL.

Are you trying to use uplink-cli?

Yes.

@storj-gerrit
Copy link

storj-gerrit bot commented Jan 16, 2023

Change https://review.dev.storj.io/c/storj/storj/+/9304 mentions this issue.

storjBuildBot pushed a commit to storj/storj that referenced this issue Jan 24, 2023
Add a docker image for uplink-cli and push it to docker hub.
We used to have this before the change to uplinkng. I'm not
sure if the pushing works, we'll see after merge.

To test, build an image with `make uplink-image`, read the tag from the
output and run normal uplink-cli commands using
`docker run -it storjlabs/uplink:df9bbceca-uplink-docker-go1.18.8-amd64 [command]`

Part of storj/uplink#109

Change-Id: I8a10aab2b778951ff42a22ba2f252c581eb66b65
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

2 participants