Skip to content

Symlink errors when re-creating container #36

@horgh

Description

@horgh

If I have an existing VM and container and I want to re-create the container, I get this error:

wstorey@penguin:~/mm_website (main)$ devpod up . --open-ide=false --devcontainer-path .devcontainer/devcontainer-gcloud.json --recreate
12:57:42 info Workspace mmwebsite already exists
12:57:42 info Creating devcontainer...
12:57:46 info Upload folder to server
12:57:46 info extract local folder: decompress: symlink ../../git/hooks/hook-chain /var/lib/toolbox/agent/contexts/default/workspaces/mmwebsite/content/.git/hooks/hook-chain: file exists
12:57:46 info error parsing workspace info: rerun as root: exit status 1
12:57:47 error Try using the --debug flag to see a more verbose output
12:57:47 fatal run agent command: Process exited with status 1

My repo has some symlinks inside it:

ubuntu@eba539873f67:/workspaces/mmwebsite$ ls -l .git/hooks/
[snip]
lrwxrwxrwx 1 ubuntu ubuntu   26 Aug 14 16:42 hook-chain -> ../../git/hooks/hook-chain
[snip]

In order to work around this, I can go into the host VM and delete the symlinks. However it'd be nice if this could be handled without having to do this.

wstorey@penguin:~$ ssh -i ~/.devpod/contexts/default/machines/mmwebsite-893bf/id_devpod_rsa devpod@localhost -p 31337
devpod@devpod-mmwebsite-893bf ~ $ cd /var/lib/toolbox/agent/contexts/default/workspaces/mmwebsite/content
devpod@devpod-mmwebsite-893bf /var/lib/toolbox/agent/contexts/default/workspaces/mmwebsite/content $ find . -type l -print0 | sudo xargs -0 /bin/rm

What do you think?

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions