Allow assigning patterns to temporary containers
See original GitHub issueAt the moment, I have to use Temporary Containers in addition to Containerise, but that is only because Containerise is missing the one feature I need from TO: temporary containers. It’d be awesome if I could e.g. create a rule like:
@(.+\.)*google(\..+)+ , TMP
which would then result in a new container be created every time I visit a matching website. The temporary containers would need to be cleaned up as well when the last tab is closed, and on domain change.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Best patterns for disposing of temporary containers
I've seen two ways of doing this so far. 1) Declaring the nativeContainer variable as a system member so that you can dispose...
Read more >Ephemeral Containers
This page provides an overview of ephemeral containers: a special type of container that runs temporarily in an existing Pod to accomplish ...
Read more >How do I force links that are not assigned to a container ...
When I open those links, I always right click and select "open in new temporary container". However unless the link is to a...
Read more >“Always Open in This Container” for entire domains/to ...
In the manage containers section I can see the list of containers I have, I can delete, rename, restrict to designated websites, give...
Read more >Best practices for writing Dockerfiles
When you run an image and generate a container, you add a new writable layer (the “container layer”) on top of the underlying...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not sure about requiring the installation of another addon to make a feature work. If @kintesh is ok with it, then sure, let’s do it that way. However it isn’t difficult to implement it ourselves
I am using TC as well as Containerise, and I’d appreciate being able to unify those two. Yes, the regexp needs work, it was just quick’n’dirty for this issue…