Using cosmos with a cpu about cosmos

[ankur-gos]

Hi, thanks for pointing this out. The CPU images are not available in docker hub currently. I'll upload them soon.

[maxaalexeeva]

@ankur-gos, thanks! Do you happen to have an estimate of when those will be available?

In the meantime, do you by any chance have any sample files that different steps of your pipeline produce? (we are looking at using the output of your system as input for our event extraction pipeline; having some sample files would help us speed things up while the images are not available). Thank you!

@cl4yton, tagging you to keep you in the loop.

[ankur-gos]

I'll probably get around to uploading the CPU images next weekend, I still need to test some of the images on CPU (we all work generally in a GPU enabled environment). As for the sample outputs, I can add that sooner with some documentation explaining what options give what outputs.

[maxaalexeeva]

@ankur-gos, that would be extremely helpful! Thank you!

[ankur-gos]

@iross I haven't had any time to work on this. If you have a free cycle and can build and push these images, that would be great.

[iross]

Sorry about the delay! They've been pushed:

Defining

BASE_IMAGE=uwcosmos/cosmos-base-cpu
DETECT_IMAGE=uwcosmos/cosmos-ingestion-cpu
WORKER_IMAGE=uwcosmos/cosmos-ingestion-cpu

in the .env file and running:

docker-compose -f deployment/docker-compose-ingest.yml -p cosmos up

Worked as expected.

[maxaalexeeva]

@iross, thank you! That's great news!

@cl4yton, fyi

[cl4yton]

Awesome, thank you Ian!

…

On Wed, Dec 16, 2020 at 10:32 AM Maria (Masha) Alexeeva < ***@***.***> wrote: *External Email* @iross <https://github.com/iross>, thank you! That's great news! @cl4yton <https://github.com/cl4yton>, fyi — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJR2PJ4ZQQS7UPGHEU7QQLSVDVKDANCNFSM4S6C5P2Q> .

-- Clayton T. Morrison Associate Professor School of Information University of Arizona web: https://ml4ai.github.io/ email: [email protected] office: 520-621-6609

[maxaalexeeva]

Hi @iross,

Do you happen to be familiar with this error?

docker-compose -f deployment/docker-compose-ingest.yml -p cosmos up
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

Creating network "cosmos_swarm_network" with driver "overlay"
Starting cosmos_scheduler_1 ... error

ERROR: for cosmos_scheduler_1  Cannot start service scheduler: network cosmos_swarm_network not found

ERROR: for scheduler  Cannot start service scheduler: network cosmos_swarm_network not found
ERROR: Encountered errors while bringing up the project.

[ankur-gos]

There's probably weird things happening with artifacts being left around from previous attempts to up the container.

If you're running locally and able to, I would restart docker. Also try running

docker system prune

before upping the compose. There could be something weird also happening with swarm mode, I would try upping the container outside swarm mode, though I doubt that's the problem.

[maxaalexeeva]

@ankur-gos , thank you for the quick response! I will try that!