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 run Error #379

Open
knolljo opened this issue Jun 28, 2023 · 3 comments
Open

Docker run Error #379

knolljo opened this issue Jun 28, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@knolljo
Copy link

knolljo commented Jun 28, 2023

When running the command specified in the documentation docker run -p 5000:5000 -p 42069:42069 -v ./data:/exa/exadir ghcr.io/varbhat/exatorrent:latest I get following output and the container exits:

Address => :5000
Directory => exadir

[ERR ] 2023/06/28 12:25:15 Error Creating Directory
@Sackbuoy
Copy link

Sackbuoy commented Jul 29, 2023

Ran into the same issue here, figured it was was an architecture issue(m2 mac) but I saw the same issue on an Ubuntu x86 machine. My setup is as follows:

Ubuntu 18.04.4
Linux Kernel 4.15.0-213-generic
Docker version 20.10.12, build e91ed57

I have permissions to the directory im using, im honestly not even sure where the error is originating from, since the Dockerfile doesnt appear to be trying to make any directories.

Plain and simple, I get this error after running these commands straight from the docs

# works just fine
docker pull ghcr.io/varbhat/exatorrent:latest 

# Fails with exact error in issue description
docker run -p 5000:5000 -p 42069:42069 -v ~/exatorrent/data:/exa/exadir ghcr.io/varbhat/exatorrent:latest

But for what its worth, it looks like building it myself and running it that way works just fine

@Sackbuoy
Copy link

Sackbuoy commented Jul 29, 2023

@knolljo I figured it out, its a permissions issue. You need to make sure the directory you are supplying it is writable by all users. so in your case it seems like running
chmod 777 ~/exatorrent/data
will solve the issue for you, though this is kind of a hack; the permissions should not need to be that lax.

I think the bigger issue here is the USER line in the Dockerfile - it hardcodes the user ID and group ID to 1000 - which I believe is the default user on *nix systems. But if the user running is not the main/first user on your system, then the container will not have permissions to use a directory created by your user.

with that in mind, you should be able to run it with the following, to specify the user with the same PUID/PGID as the one that created the directory:
docker run -p 5000:5000 -p 42069:42069 -u $(id -u ${USER}):$(id -g ${USER}) -v /path/to/directory:/exa/exadir ghcr.io/varbhat/exatorrent:latest

@varbhat any thoughts or preferences?

@nlevee
Copy link
Collaborator

nlevee commented Nov 7, 2023

@Sackbuoy It's fix in the PR #404

Startup without parameters is working now.

We have to fix now volume mounted

@nlevee nlevee added the bug Something isn't working label Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants