Image check failed: DigitalOcean directory detected

[gustavosbarreto]

Output log:

digitalocean:
    digitalocean:
    digitalocean: Checking all user-created accounts...
    digitalocean:
    digitalocean:
    digitalocean: Checking the root account...
    digitalocean: [PASS] User root has no password set.
    digitalocean: [ OK ] User root has no SSH keys present
    digitalocean: [PASS] root's Bash History appears to have been cleared
    digitalocean: [FAIL] DigitalOcean directory detected.
    digitalocean: To uninstall the agent and remove the DO directory: 'sudo apt-get purge droplet-agent'
    digitalocean:
    digitalocean:
    digitalocean: ---------------------------------------------------------------------------------------------------
    digitalocean: Scan Complete.
    digitalocean: One or more tests failed.  Please review these items and re-test.
    digitalocean: ---------------------------------------------------------------------------------------------------
    digitalocean: 7 Tests PASSED
    digitalocean: 2 WARNINGS
    digitalocean: 1 Tests FAILED
    digitalocean: ---------------------------------------------------------------------------------------------------

Steps to reproduce:

git clone https://github.com/digitalocean/marketplace-partners.git
export DIGITALOCEAN_TOKEN=...
packer build marketplace-image.json

What is expected?

A successfully build.

Extra information:

Since this PR #156 the build seems to fail.

[gustavosbarreto]

Related to: #164

[afeiszli]

I'm encountering the same issue.

[actorTian]

I'm encountering the same issue.

[Cristy94]

Any updates? Running the recommended command sudo apt-get purge droplet-agent doesn't fix the issue.

[Cristy94]

After adding this to cleanup.sh: rm -rf /opt/digitalocean fixes the error, but I think breaks onboot and MOTD script execution.

[stefanpejcic]

don't enable

Add improved metrics monitoring and alerting (free)

when starting the droplet

[Cristy94]

don't enable

Add improved metrics monitoring and alerting (free)

when starting the droplet

I use packer to create the build, so I don't enable any alerting.

[stefanpejcic]

Problem does not occur on build process, but when you run a droplet with this enabled:

For me, when I dont enable it I dont have this problem.