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

Setup VENV_PATH #12

Open
chrisoutwright opened this issue May 4, 2024 · 1 comment
Open

Setup VENV_PATH #12

chrisoutwright opened this issue May 4, 2024 · 1 comment

Comments

@chrisoutwright
Copy link

After having build locally, with

docker buildx bake -f docker-bake.hcl

to which actual venv should this be pointing?
I have no such workspace, where is this supposed to be?
VENV_PATH="/workspace/venvs/llava

 2024-05-04 13:07:15 Template version: 1.6.0
2024-05-04 13:07:15 venv: /workspace/venvs/llava
2024-05-04 13:07:15 RUNPOD_PUBLIC_IP is not set. Skipping FileZilla configuration.
2024-05-04 13:07:15 Updating rclone...
2024-05-04 13:07:18 Exporting environment variables...
2024-05-04 13:07:18 Container is READY!
2024-05-04 13:07:15 /pre_start.sh: line 2: $'\r': command not found
2024-05-04 13:07:15 /pre_start.sh: line 6: $'\r': command not found
2024-05-04 13:07:15 /pre_start.sh: line 9: $'\r': command not found
2024-05-04 13:07:15 /pre_start.sh: line 16: syntax error near unexpected token `$'{\r''
'024-05-04 13:07:15 /pre_start.sh: line 16: `sync_apps() {

I am using a empty dir right now, but this is supposed to be the actual venv somewhere outside the docker? I went through the readme several times, I must have missed a step elsewhere.

@ashleykleynhans
Copy link
Owner

/workspace is the persistent storage that is attached to the container. Any specific reason why you want to build the docker image rather than using the already built one?

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