globus / globus/globus-compute

Bind a container ID to an Endpoint

Open
#356 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
162
Forks
53
Avg merge
15h 29m
Merged PRs (30d)
26

Description

_As an endpoint owner on a system that support shifter I want to be able to manually map a container ID to my workers so I can run functions that depend on that container_

Contributor guide

Open the contributing guide

Research direction

The issue names endpoint owners, workers, container IDs, and Shifter support but provides no files, tests, or entry points. Start by locating the endpoint and worker implementation and how container-related configuration is handled. Clarify the expected API, persistence, and mapping behavior; done should allow an owner to bind a container ID to workers and run functions that depend on it.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.