Files
weave/website/tasks/weave-docker-api/launching-without-proxy.md
T
Raj Chaudhuri e2db8a25bd Added documentation website content, and a workflow to publish it to GitHub Pages
* Copied, rearranged and modified the contents of the old site directory for Jekyll static site generator, into the website directory
* Added some Jekyll-specific things for looks, including:
  * _config.yaml, Gemfile.* and 404.html files
  * _data, _layouts and assets directories and their content
* Added .github/workflows/github-pages-publish.yml workflow
2024-03-18 20:37:53 +05:30

769 B

title, menu_order, search_type
title menu_order search_type
Launching Containers With Weave Run (without the Proxy) 60 Documentation

In prior versions of Weave Net, we supported a command weave run which would run a container and attach it to the Weave Network.

This command always had limitations, and now we have Docker plugins and the Weave Net Docker API Proxy which do not have those limitations, we have removed weave run.

If you have scripts using weave run, you can achieve exactly the same effect by combining docker run and weave attach; see [Dynamically Attaching and Detaching Containers]({{ '/tasks/manage/dynamically-attach-containers' | relative_url }}) for details.

The weave start and weave restart commands have also been removed, for the same reasons.