criteo / mesos-term Goto Github PK

Current permissions allow following scheme:

• members of MESOS_TERM_SUPER_ADMINS groups can connect on every container
• members of MESOS_TERM_ALLOWED_TASK_ADMINS groups can connect on containers if MESOS_TERM_DEBUG_GRANTED_TO contains exactly the same group

I'd like to be able to define following scenario:

• members of MESOS_TERM_SUPER_ADMINS groups can connect on every container (no change)
• members of MESOS_TERM_ALLOWED_TASK_ADMINS groups can connect on containers if they belong to a group listed by MESOS_TERM_DEBUG_GRANTED_TO

The difference is that we could configure a large group of users to connect to their container only (let's say a group called "operators") without listing every group that should be whitelisted in MESOS_TERM_ALLOWED_TASK_ADMINS or activating MESOS_TERM_ENABLE_PER_APP_ADMINS (which would give everyone access to their container)

Would that make sense?

What do you think it'll take to add docker exec support ?

Text displayed in mesos-term can be copied in chrome (and chromium) but not in firefox.

Firefox 67.0 64-bits on linux.

When launching an editor in mesos-term

• nano returns an error Error opening terminal: unknown., we have to manually set the TERM env TERM=linux nano
• vim, nano, and I guess most editors use 24 lines and 80 cols, regardless the window size.

2 questions :
1 / shouldn't TERM=linux be injected in the environment if not present ?
2 / how can we use the full window with text editors ?