Before you start
You need container-reading permission and the corresponding write capability for changes. Review the intended workload, image, limits, persistence and network exposure before creation or removal.
What to do
- Open Containers and inspect the Containers, Images, Volumes and Networks tabs. Identify the exact container by name, identifier and image.
- When Run container is available, review the name, image, memory and CPU limits. Enter port mappings and command arguments as JSON arrays and environment variables as a JSON object, as required by the form.
- Read the hosting-location and port-binding description before submitting. A published container port is not proof that the intended public route or external access is configured.
- Inspect the resulting container state and ports. Use Start, Restart, Stop or Logs only for the intended container, then verify its application separately.
- Use Delete only after reviewing the exact target confirmation and preserving the intended data. Do not assume that removing a container is equivalent to removing its image, volumes, networks or all application data.
What happens next
You can inspect the container inventory and the accepted action's result. The running state alone does not establish application health, persistent-data safety or public reachability.
If something goes wrong
Check JSON syntax, image availability, start arguments, limits, port mappings and logs if creation or startup fails. Inspect the current inventory before repeating an uncertain creation. Contact the infrastructure administrator when persistence or routing is unclear; do not include environment secrets in screenshots or support messages.
