Comment by Rob Allen (JIRA)

This is related to the vboxfs file system.

I changed to using nfs, and it works:

config.vm.synced_folder ".", "/vagrant", type: "nfs"

it would be nice if this worked with vboxfs though!

(I wasted hours on this!)

@mxcl any idea where this is coming from?

`get.swift` does the rename. But I couldn't guess why it fails. I'll test it out in my vmware VM which has shared folders first.

Comment by Marcus Kida (JIRA)

Same problem here using Docker version 1.9.1, build a34a1d5 with Ubuntu 14.04.

warning: refname '0.2.3' is ambiguous.
warning: refname '0.2.3' is ambiguous.
Using version 0.2.3 of package Curassow
warning: refname '0.2.1' is ambiguous.
warning: refname '0.2.1' is ambiguous.
Using version 0.2.1 of package Nest
warning: refname '0.2.2' is ambiguous.
warning: refname '0.2.2' is ambiguous.
Using version 0.2.2 of package Inquiline
warning: refname '0.4.0' is ambiguous.
warning: refname '0.4.0' is ambiguous.
Using version 0.4.0 of package Commander
warning: refname '1.2.0' is ambiguous.
warning: refname '1.2.0' is ambiguous.
Using version 1.2.0 of package Safe
error: rename error: File exists (17): /app/Packages/Nest -> /app/Packages/Nest-0.2.1

In case you want a detailed description on how to reproduce this, please tell me. Shouldn't be too hard though by just spinning up a container and mounting a local folder into the FS trying to build the swift project from there.

Sorry I haven't had a chance to look into this yet.

I have pushed a fix for this: 629a93c

Let me know if it works. Thanks.

Comment by Jay Buffington (JIRA)

I've confirmed this fixing the issue I was seeing related to this.

Comment by Marcus Kida (JIRA)

Sorry for not getting back earlier @mxcl, just confirmed this fixed my issues in an dockerized aufs environment. Chapeau.

np! Thanks for confirming.

Comment by tanner0101 (JIRA)

I'm experiencing a similar issue with the `07-29` toolchain. I have a folder mounted from Windows 10 to a Docker Ubuntu 14.04 container.

root@d5f0ce7420c1:/vapor/Hello# swift build
<unknown>:0: error: could not acquire lock file for module 'SwiftShims': failed to create link /vapor/Hello/.build/debug/ModuleCache/19LPOOIZSL9B7/SwiftShims-1KFO504FT44T.pcm.lock to /vapor/Hello/.build/debug/ModuleCache/19LPOOIZSL9B7/SwiftShims-1KFO504FT44T.pcm.lock-53339b52: Protocol error
<unknown>:0: error: missing required module 'SwiftShims'
<unknown>:0: error: build had 1 command failures
error: exit(1): /usr/bin/swift-build-tool -f /vapor/Hello/.build/debug.yaml

root@d5f0ce7420c1:/vapor/Hello# env IS_SWIFTPM_TEST=1 swift build
Compile Swift Module 'Hello' (1 sources)
<unknown>:0: error: error opening '/vapor/Hello/.build/debug/Hello.build/Hello~partial.swiftmodule' for output: Text file busy
<unknown>:0: error: build had 1 command failures
error: exit(1): /usr/bin/swift-build-tool -f /vapor/Hello/.build/debug.yaml

This sounds like it is actually an issue in the compiler's module handling mechanism. Maybe we should try to reduce it to a compiler-specific test case.

Comment by Jayaprakash (JIRA)

tannernelson (JIRA User) Hi, Did you solved this issue? I am facing the same error when I mount the folder and run "swift hello.swift".

Error message:
<unknown>:0: error: could not acquire lock file for module 'SwiftShims'
<unknown>:0: error: missing required module 'SwiftShims'