You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
ship init /path/to/yaml/files breaks upon reaching the kustomize step with an error in debug.log: {"caller":"github.com/replicatedhq/ship/pkg/lifecycle/daemon/routes_navcycle_getstep.go","err":"initial kustomize run: write base kustomization: Base directory is empty","event":"preExecute.fail","level":"error","ts":"2019-02-25T21:38:10.984896Z"}
Information
Ship version: 0.34.0
Docker version: ...
Command line run: ship init ~/go/src/github.com/replicatedhq/test-charts/plain-k8s/
Steps to reproduce the behavior
prepare a folder of kubernetes yaml locally
run ship init with the absolute path to that folder
observe failure upon reaching the kustomize step
The text was updated successfully, but these errors were encountered:
This is related to the fact that go-getter uses symlinks for local files, and so instead of a folder base there is a symlink. Some of the libraries we use do not seem to appreciate this fact, and we should really be copying the files anyways in order to avoid modifying the source.
Unfortunately go-getter doesn't yet support copying directories (see hashicorp/go-getter#169) so we may have to handle that case ourselves for now.
Expected behavior
ship init /path/to/yaml/files
should workActual behavior
ship init /path/to/yaml/files
breaks upon reaching the kustomize step with an error in debug.log:{"caller":"github.com/replicatedhq/ship/pkg/lifecycle/daemon/routes_navcycle_getstep.go","err":"initial kustomize run: write base kustomization: Base directory is empty","event":"preExecute.fail","level":"error","ts":"2019-02-25T21:38:10.984896Z"}
Information
ship init ~/go/src/github.com/replicatedhq/test-charts/plain-k8s/
Steps to reproduce the behavior
ship init
with the absolute path to that folderThe text was updated successfully, but these errors were encountered: