microsoft / microsoft/pai

Using paictl commands without dev-box

Open
#5,668 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
554
Avg merge
20h 42m
Merged PRs (30d)
14

Description

Hello, I have started my own cluster following you admin guide. In the guide, dev-box container was not used so my cluster and service are deployed without the dev-box. However, it seems when I want to change configuration, paictl commands need to work and these commands do not seem to work without the dev-box container.

If i run the following command with my cluster and service already online,

sudo docker run -itd
-e COLUMNS=$COLUMNS -e LINES=$LINES -e TERM=$TERM
-v /var/run/docker.sock:/var/run/docker.sock
--pid=host
--privileged=true
--net=host
--name=dev-box
openpai/dev-box:

certain folders and files such as "pai-deploy" are not in the docker container.

If I want to run paictl commands, should I go through the installation process inside the docker image?

Organization Name:

Short summary about the issue/question:

Brief what process you are following:

How to reproduce it:
go through steps in the installation guide
https://openpai.readthedocs.io/en/latest/manual/cluster-admin/installation-guide.html
and try paictl commands in /pai

OpenPAI Environment:

  • OpenPAI version: v1.8.0
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Hardware (e.g. core number, memory size, storage size, GPU type etc.):
  • Others:

Anything else we need to know:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the cluster-admin installation guide and the paictl commands in /pai, then compare the documented dev-box workflow with a cluster deployed without that container. Determine whether the standalone workflow is supported and document or correct the expected steps; completion should make paictl usable without dev-box or clearly explain that it is required.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
cli, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.