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

deploy.sh is broken; wrong directory for the unpack? #1193

Closed
jlewi opened this issue Jul 13, 2018 · 1 comment
Closed

deploy.sh is broken; wrong directory for the unpack? #1193

jlewi opened this issue Jul 13, 2018 · 1 comment

Comments

@jlewi
Copy link
Contributor

jlewi commented Jul 13, 2018

It looks like the directory it got unpacked to didn't match the move

+ pwd
+ KUBEFLOW_REPO=/home/jlewi/git_kubecon_gh_demo/kubeflow_repo
+ KUBEFLOW_VERSION=0.2.1
+ [[ ! -d /home/jlewi/git_kubecon_gh_demo/kubeflow_repo ]]
+ '[' 0.2.1 == master ']'
+ TAG=v0.2.1
+ curl -L -o /tmp/kubeflow.0.2.1.tar.gz https://github.com/kubeflow/kubeflow/archive/v0.2.1.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   125    0   125    0     0     78      0 --:--:--  0:00:01 --:--:--    78
100 5307k    0 5307k    0     0   703k      0 --:--:--  0:00:07 --:--:-- 1382k
+ tar -xzvf /tmp/kubeflow.0.2.1.tar.gz -C /tmp
+ mv /tmp/kubeflow-v0.2.1 /home/jlewi/git_kubecon_gh_demo/kubeflow_repo
mv: cannot stat '/tmp/kubeflow-v0.2.1': No such file or directory
...

It looks like the v is being stripped out of the unpacked files.
@jlewi
Copy link
Contributor Author

jlewi commented Jul 13, 2018

Workaround is too manually download it before running the script

export KUBEFLOW_REPO=....
curl -L -o /tmp/kubeflow.${KUBEFLOW_VERSION}.tar.gz https://github.com/kubeflow/kubeflow/archive/${TAG}.tar.gz
tar -xzvf /tmp/kubeflow.${KUBEFLOW_VERSION}.tar.gz  -C /tmp
mv /tmp/kubeflow-${KUBEFLOW_VERSION} "${KUBEFLOW_REPO}"

${KUBEFLOW_REPO}/scripts/deploy.sh

@jlewi jlewi closed this as completed Jul 13, 2018
surajkota pushed a commit to surajkota/kubeflow that referenced this issue Jun 13, 2022
)

* For the GCP blueprint the Kubeflow cluster should use the
  stable release channel rather than using minMasterVersion

* Also add node autoprovisioning settings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant