[HN Gopher] Yacht - A web interface for managing Docker containers
       ___________________________________________________________________
        
       Yacht - A web interface for managing Docker containers
        
       Author : indigodaddy
       Score  : 51 points
       Date   : 2022-04-27 07:43 UTC (15 hours ago)
        
 (HTM) web link (yacht.sh)
 (TXT) w3m dump (yacht.sh)
        
       | sandreas wrote:
       | I prefer lazydocker[1].
       | 
       | 1: https://github.com/jesseduffield/lazydocker
        
       | prtkgpt wrote:
       | This is awesome! Can I help you fix the website a tiny bit to
       | make it top notch and get the founders started with a content
       | strategy & machine?
       | 
       | This is purely help, 100% free. So feel free to reach out. :)
        
       | lesgobrandon wrote:
        
       | p2hari wrote:
       | Very nice. I am thinking this to be on lines of Bitnami ...Nice
       | to see basic server info also on the dashboard. Would definitely
       | try this.
        
       | ourmandave wrote:
       | It froze when I tried to log in with my username: oligarch.
        
       | 293984j29384 wrote:
       | The lack of screenshots or useful videos other than the tiny
       | video that can't be controlled on the doc page is poor web
       | design. If you want people to use your GUI tool, they need to be
       | able to see it first.
        
         | tyingq wrote:
         | The small video on imgur, which makes it a little easier to
         | zoom in, but it's pretty low res:
         | 
         | https://imgur.com/a/BRmYDfF
         | 
         | https://i.imgur.com/2U1JvXd.mp4
        
         | pineconewarrior wrote:
         | There is a video at the top of the docs, but I agree it should
         | be featured on the landing page
        
         | Bedon292 wrote:
         | Yeah, having trouble figuring out why I would want to use this
         | tool. What problem is it trying to solve? How does it
         | differentiate itself from other tools out there? I just get a
         | list of features and a tiny video.
        
         | shantnutiwari wrote:
         | Yeah, I have no idea how it works. The docs talk about
         | "container templating"-- what?
        
       | vinnymac wrote:
       | I have used portainer in the past to manage containers, curious
       | whether this offers something different or if they are fairly
       | similar.
       | 
       | https://www.portainer.io/
        
         | croon wrote:
         | I don't use it anymore since I find CLI faster, and am starting
         | to migrate to Nomad, but my main gripe with Portainer was the
         | spotty compose support, that I basically had to write them
         | outside, launch them, and then have them show up in Portainer,
         | kind of defeating the point of the frontend.
         | 
         | If the compose support in this is better I could see the value
         | for people just dipping their toe in.
        
           | cosmotic wrote:
           | Unless I'm missing something, one common use case the GUI
           | makes a lot faster is issuing commands that need
           | container/image/volume ids. Opening a terminal in a container
           | is a click or two instead of two commands where the second
           | requires visually parsing some large screen of text and
           | carefully transcribing a few characters. It also hard to
           | remember all the command line flags and their inconsistencies
           | (which commands support -a and which do not?)
        
           | blue_cookeh wrote:
           | It got significantly better in an update towards the end of
           | last year (IIRC). Can also use GitHub as a source of truth
           | for stacks now, and has webhooks etc.
        
         | tgtweak wrote:
         | Been using portainer for a while and it's been great.
        
       | [deleted]
        
       | encryptluks2 wrote:
       | Neat, but it is a huge security issue to mount your Docker socket
       | into a container, essentially giving it full access to all your
       | containers. Shouldn't this be limited to bare API permissions as
       | opposed to full access?
        
         | lima wrote:
         | Yes, it essentially gives root privileges to it.
         | 
         | I suppose that's intended in this case.
        
       ___________________________________________________________________
       (page generated 2022-04-27 23:03 UTC)