Open kumy opened 8 years ago
As a workaround, I've manually logged into docker image, installed missing libs then run from that
This may be a bug while generating the image, I'll force a rebuild (I built a local version from the same sources and they seem just fine).
Same error with that build. @samueltardieu someone at work proposed such change, could you please give it a try?
Got the same error while building the image locally
Failed to rename directory /opt/android-sdk-linux/extras/android/m2repository to /opt/android-sdk-linux/temp/ExtraPackage.old01.
Failed to create directory /opt/android-sdk-linux/extras/android/m2repository
Installing Archives:
Preparing to install archives
Downloading SDK Platform Android 5.1.1, API 22, revision 2
Installing SDK Platform Android 5.1.1, API 22, revision 2
Installed SDK Platform Android 5.1.1, API 22, revision 296%)
Downloading SDK Platform Android 4.4.2, API 19, revision 4
Installing SDK Platform Android 4.4.2, API 19, revision 4
Installed SDK Platform Android 4.4.2, API 19, revision 497%)
Downloading Google APIs, Android API 23, revision 1
Installing Google APIs, Android API 23, revision 1
Installed Google APIs, Android API 23, revision 189%)
Downloading Local Maven repository for Support Libraries, revision 26
Installing Local Maven repository for Support Libraries, revision 26
Failed to rename directory /opt/android-sdk-linux/extras/android/m2repository to /opt/android-sdk-linux/temp/ExtraPackage.old01.
Failed to create directory /opt/android-sdk-linux/extras/android/m2repository
Downloading Android Support Library, revision 23.2
Installing Android Support Library, revision 23.2
Failed to rename directory /opt/android-sdk-linux/extras/android/support to /opt/android-sdk-linux/temp/ExtraPackage.old01.
Failed to create directory /opt/android-sdk-linux/extras/android/support
Downloading Google APIs, Android API 22, revision 1
Installing Google APIs, Android API 22, revision 1
Installed Google APIs, Android API 22, revision 189%)
Downloading Google APIs Intel x86 Atom_64 System Image, Google Inc. API 23, revision 12
Installing Google APIs Intel x86 Atom_64 System Image, Google Inc. API 23, revision 12
Installed Google APIs Intel x86 Atom_64 System Image, Google Inc. API 23, revision 1299%)
Updated ADB to support the USB devices declared in the SDK add-ons.
Stopping ADB server succeeded.
Starting ADB server succeeded.
Done. 5 packages installed.
---> 3539967e0e72
df -h
as requested
Filesystem Size Used Avail Use% Mounted on
rootfs 1008G 393G 564G 42% /
none 1008G 393G 564G 42% /
tmpfs 2.0G 0 2.0G 0% /dev
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/mapper/RAID-4T 3.6T 3.0T 629G 83% /srv
/dev/mapper/DATA-DOWN 1008G 393G 564G 42% /etc/hosts
shm 64M 0 64M 0% /dev/shm
tmpfs 2.0G 0 2.0G 0% /proc/kcore
tmpfs 2.0G 0 2.0G 0% /proc/timer_stats
It seem to be a problem with hardlinks while moving directory by the android sdk installer which isn't supported by aufs. I was on aufs. I'll test with btrfs.
So we can close this one, right?
As images generated at hub docker level are "wrong", I would leave it open until something is fixed. We only have the reason and a workaround (build locally without aufs Storage Driver), no?
Latest build from new executors fails with errors like:
The docker image doesn't include:
From logfile:
Inside the docker instance, the directories are empty