-
Notifications
You must be signed in to change notification settings - Fork 24
Authorisation manifest creation error #30
Comments
The conf directory is in the host and it is mount bind into the container. |
Thanks. The conf directory is on the host and declared as RW, so no troubles there. The problem is that the authorisation service cannot write to the manifest file somehow (IOException) in the conf/adb directory if it is on a Windows host. A workaround is to create a symbolic link back to the container for the conf/adb directory. Thus, the conf directory contents are on the host, but the adb directory is stored in the container. When done this way, the authorisation exception does not occur. I have included the section from the engine_error.log below: Nov 28, 2016 9:44:22 AM com.google.common.util.concurrent.ServiceManager$ServiceListener failed Exception in thread "AuthorizedStorageService STARTING" java.lang.RuntimeException: java.io.IOException: IO error: /var/crashplan/app/conf/adb: Invalid argument |
When 'authorizing' the Crashplan client, Crashplan creates an 'adb' folder in the conf directory. When this is a shared volume on Windows, an IO error occurs trying to write the Manifest file.
A similar issue can be found here: Level/levelup#222
A possible way around this is for the adb directory to be kept in the container volume (e.g. via a symbolic link in the conf directory).
The text was updated successfully, but these errors were encountered: