search

SecurityRiskAdvisors / VECTR

VECTR is a tool that facilitates tracking of your red and blue team testing activities to measure detection and prevention capabilities across different attack scenarios
1.36k stars 161 forks source link

License issue on install #141

Closed mark1973ryan closed 3 years ago

mark1973ryan commented 3 years ago

Hi,

I'm installing from scratch as per the docs on a licensed Rhel server and I'm getting the following. Anyone come across what this means?

2021-08-26T09:42:13.877751758Z container destroy 789906d0dd1f355f296b595f83165253e9748fb4f506f27f2f0ce5f5eb330c04 (architecture=x86_64, authoritative-source-url=registry.access.redhat.com, build-date=2020-03-24T19:35:24.851991, com.redhat.build-host=cpt-1005.osbs.prod.upshift.rdu2.redhat.com, com.redhat.component=rhel-server-container, com.redhat.license_terms=https://www.redhat.com/en/about/red-hat-end-user-license-agreements, description=The Red Hat Enterprise Linux Base image is designed to be a fully supported foundation for your containerized applications. This base image provides your operations and application teams with the packages, language runtimes and tools necessary to run, maintain, and troubleshoot all of your applications. This image is maintained by Red Hat and updated regularly. It is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. When used as the source for all of your containers, only one copy will ever be downloaded and cached in your production environment. Use this image just like you would a regular Red Hat Enterprise Linux distribution. Tools like yum, gzip, and bash are provided by default. For further information on how this image was built look at the /root/anacanda-ks.cfg file., distribution-scope=public, image=docker-compose:latest, io.k8s.description=The Red Hat Enterprise Linux Base image is designed to be a fully supported foundation for your containerized applications. This base image provides your operations and application teams with the packages, language runtimes and tools necessary to run, maintain, and troubleshoot all of your applications. This image is maintained by Red Hat and updated regularly. It is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. When used as the source for all of your containers, only one copy will ever be downloaded and cached in your production environment. Use this image just like you would a regular Red Hat Enterprise Linux distribution. Tools like yum, gzip, and bash are provided by default. For further information on how this image was built look at the /root/anacanda-ks.cfg file., io.k8s.display-name=Red Hat Enterprise Linux 7, io.openshift.tags=base rhel7, name=wonderful_hugle, release=265, summary=Provides the latest release of Red Hat Enterprise Linux 7 in a fully featured and supported base image., url=https://access.redhat.com/containers/#/registry.access.redhat.com/rhel7/images/7.8-265, vcs-ref=8f18087f5b36eeba2435483c40ce5de5b25c2eff, vcs-type=git, vendor=Red Hat, Inc., version=7.8)

SRAPSpencer commented 3 years ago

At what phase of the deployment are you getting this?

mark1973ryan commented 3 years ago

As soon as I hit the compose command. I've stripped it down just to the Mongo container and I'm still getting it. The issue is we don't have compose on the box so we run from compose from a container. It may be this that is causing the issue. It worked previously.

SRAPSpencer commented 3 years ago

It seems like this presents itself whenever you're working with containers that aren't "RHEL Certified". Does it prevent the containers from coming up and working?

SRAPSpencer commented 3 years ago

As soon as I hit the compose command. I've stripped it down just to the Mongo container and I'm still getting it. The issue is we don't have compose on the box so we run from compose from a container. It may be this that is causing the issue. It worked previously.

Sorry I missed this part, you're trying to run docker inside of docker? Containers inside of containers can be weird and we don't officially support that. We only officially support running docker and docker compose directly on the host OS.