mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1016] Docker docs #2566
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2566
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @silversword411 on GitHub (Mar 22, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1016
Originally assigned to: @silversword411 on GitHub.
Add to docs:
Clean install docker commands:
sudo docker-compose stop
(If TRMM is the only thing on this docker host you can use below commands)
sudo docker rm -f $(sudo docker ps -a -q)
sudo docker volume rm $(sudo docker volume ls -q)
sudo docker network prune
If you are running other things on the same host you will have to remove all the images and volumes manually. Once that is complete you can run sudo docker network prune to cleanup the networks no longer in use. (This will remove ALL docker networks no longer used, Not just TRMM networks)
Then following the guide TRMM will rebuild itself when you run
sudo docker-compose up -d (edited)
I botched a new install of the docker style and could not get it to come up due to a "Network" error untill i removed the docker networks and let them rebuild. The above removes all the existing docker containers and network and rebuilds it all. Might be helpful to others to ensure a clean start.
@ninjamonkey198206 commented on GitHub (Aug 5, 2022):
@silversword411 bump
Looking through old issues to see if any could be closed or resolved, found this
@silversword411 commented on GitHub (Aug 5, 2022):
Yeah, I think this was just for expanding docs, and a todo for those that wanted to try their hand at docs updating.
You think what's up is enough? Docker now "unsupported" might just be able to forget
@ninjamonkey198206 commented on GitHub (Aug 5, 2022):
I mean, I have been meaning to add to them a bit, but we can probably get rid of the open issue.