Docker Community Forums

Share and learn in the Docker community.

Installation fails - Avast File Protection detects Win64:Vitro in vmlinuz64


(Chris Jones) #1

Expected behavior

Installation to succeed with Avast File Protection enabled.

Actual behavior

Installation failes with Avast File Protection enabled.
Succeeds with it disabled.

Information


  • the output of:
    • pinata diagnose -u on OSX
      OS X: version 10.11.4 (build: 15E65)
      Docker.app: version v1.11.1-beta13.1
      Running diagnostic tests:
      [OK] Moby booted
      [OK] driver.amd64-linux
      [OK] vmnetd
      [OK] osxfs
      [OK] db
      [OK] slirp
      [OK] menubar
      [OK] environment
      [OK] Docker
      [OK] VT-x
      Docker logs are being collected into /tmp/20160606-102508.tar.gz
      Most specific failure is: No error was detected

Your unique id is: 0DD5EA1D-3FA5-402B-9355-7F313BC45E73
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Mac OS X 10.11.4, running Avast Mac Security 2015, attempt to upgrade from Docker 1.11.1-beta13.1 to 1.11.1-beta-14

(Matteocng) #2

I’m affected by this exact issue too.

The output of pinata diagnose -u

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160606-170806.tar.gz
Most specific failure is: No error was detected
Your unique id is: 865C7C71-ED0B-48D4-A699-607943EBB0BE
Please quote this in all correspondence.

Avast version: 11.11 (46429)
Avast virus definitions version: 16060600
"File System Shield" enabled. “Mail Shield” and “Web Shield” disabled.


(Georgecook) #3

Yep. Just got the same error and blocked virus alert.

$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160606-084404.tar.gz
Most specific failure is: No error was detected
Your unique id is: 4F1A1552-7203-464D-9FE5-8F7A19977AC7
Please quote this in all correspondence.


(Aio1108) #4

I have the same issue.

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160606-215341.tar.gz
Most specific failure is: No error was detected
Your unique id is: AD5465C2-C50C-469C-90BD-945C2E5250D0
Please quote this in all correspondence.

Avast version: 11.11 (46429)
Virus definitions version: 16060600


(Luis Herrera) #5

Same behaviour. Antivirus claiming that /Users/Luis/Library/Caches/com.docker.docker/Sparkle/Docker 8623/Docker.app/Contents/Resources/moby/vmlinuz64 is infected with Win64:Vitro. Apparently, Win64: Vitro is a kind of ransomware that can get encrypted files on the infected computers in …Windows. False positive?


(David) #6

I have this problem as well:

$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160606-175133.tar.gz
Most specific failure is: No error was detected
Your unique id is: C61E5620-B70E-4DBA-AE4C-B74AF7466E63
Please quote this in all correspondence.

Avast version: 11.11 (46429)
Virus definition updates: 16060600


(Frenchben) #7

I just pushed the file to an online virus scanner which did not detect any virus:
https://www.virustotal.com/en/file/304ed8f35e83c528279e294ac274e3088a084af42662884b4834bab10ef553d5/analysis/1465239434/

and

Can one of you (having the issue) do the same thing so that we can compare the results? (file is about ~5mb)


(Kmfk) #8

@frenchben Had the same issue as above with the failed install with Avast flagging that file. However, my ~/Library/Caches/com.docker.docker/Sparkle directory is now empty.

Having Docker check for an update now either says that beta13.1 is the latest or fails: https://www.dropbox.com/s/kb8d8qwquh5y2w4/Screenshot%202016-06-06%2013.04.11.png?dl=0

Not sure about anyone else, but not sure if we can check this?


(Fidelleon) #9

Same here…

$ pinata diagnose -u
OS X: version 10.11.6 (build: 15G7a)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160606-193502.tar.gz
Most specific failure is: No error was detected


(Vasili4) #10

same here

➜ ~ pinata diagnose -u OS X: version 10.11.5 (build: 15F34) Docker.app: version v1.11.1-beta13.1 Running diagnostic tests: [OK] Moby booted [OK] driver.amd64-linux [OK] vmnetd [OK] osxfs [OK] db [OK] slirp [OK] menubar [OK] environment [OK] Docker [OK] VT-x


(Frenchben) #11

A new update was pushed just recently which was checked against avast here without any issues.
Can you re-try to update?
@vasili4 @davidsblog @matteocng @matteocng @kmfk @chrisjones77 @fidelleon @georgecook @aio1108


(Kmfk) #12

Can confirm the recent version installed with out issue.


(Georgecook) #13

Installed without error with hotfix version.


(Vasili4) #14

works like magic. Thanks


(Aio1108) #15

Problem solved. Updated without issue. Thanks a lot.


(Fidelleon) #16

Works like a charm for me, thanks!


(Matteocng) #17

Thanks, problem solved.


(Vasili4) #18

Latest 1.12.1-beta25 has same issue.
Just opened github Issue for that


(Paulne) #19

Yep, me too:


(Matteocng) #20

Same issue:

Version 1.12.1-beta24 (build: 11525)
OS X 10.11.6 (15G31)
Avast version: 11.17 (46792)
Avast virus definitions: 16090701