IBM-Swift / swift-buildpack

IBM Cloud buildpack for Swift
BSD 3-Clause "New" or "Revised" License
32 stars 31 forks source link

Disk Quota Exceeded #123

Open schlingding opened 4 years ago

schlingding commented 4 years ago

18.04 runs into Disk Quota Exceeded errors during Copying binaries to 'bin' phase.

Tried raising disk space with no change.

Using: buildpack: https://github.com/IBM-Swift/swift-buildpack#2.2.0 stack: cflinuxfs3

Dependencies example which can cause this issue: dependencies: [ .package(url: "https://github.com/IBM-Swift/Kitura.git", .upToNextMinor(from: "2.8.1")), .package(url: "https://github.com/IBM-Swift/HeliumLogger.git", .upToNextMajor(from: "1.9.0")), .package(url: "https://github.com/IBM-Swift/CloudEnvironment.git", .upToNextMajor(from: "9.1.0")), .package(url: "https://github.com/IBM-Swift/Health.git", .upToNextMajor(from: "1.0.5")), .package(url: "https://github.com/IBM-Swift/SwiftyRequest.git", .upToNextMajor(from: "3.0.0")), .package(url: "https://github.com/IBM-Swift/Kitura-OpenAPI.git", from: "1.3.0"), .package(url: "https://github.com/RuntimeTools/SwiftMetrics.git", .upToNextMajor(from: "2.6.4")), .package(url: "https://github.com/ianpartridge/swift-backtrace", .upToNextMajor(from: "1.1.1")) ]

mbarnach commented 4 years ago

I have the same issue with similar dependencies. I've tried to remove as much as possible, but I think the problem is related to the inclusion of SwiftyRequest. Nevertheless, when I compile on my machine, the size is ~640MB, so quite far from the 2GB I allocate. Any workaround that?

2meeltd commented 4 years ago

Had same problem. Tried get-started-app on cloud foundry. In the manifest they have added at end

env: SWIFT_BUILD_DIR_CACHE: false

This solved my problem. Still a bit worrying as support was saying the will not increase the 2GB limit.

mbarnach commented 4 years ago

In my case, it didn't solved the problem unfortunately. My current work-around is to use a Docker image, and push the image. Not ideal, but it does the job so far.

AlexChekanov commented 4 years ago

Have anyone found a solution?

SWIFT_BUILD_DIR_CACHE: false doesn't help, unfortunately.