Install with Docker CLI

Apps and Virtualization
, , ,
1

Hello, I’m looking into installing custom apps from Docker images but I’m having trouble to translate the Docker commands CLI into Truenas interpretation. Is it possible to make a complete installation of a custom app with a Docker CLI or not?

2

I see this a tagged dragonfish if that is the version you are on then NO… unless you use jailmaker and install docker in debian…

HOWEVER Truenas Scale EE is in RC release phase and it has native docker… You can get the RC now, but it is being release at the end of this month Oct 29th

1 Like
3

Ok, so for example I want to install binhex/arch-qbittorrentvpn because it has VPN support. The Docker image has a lot of command to do for it works. I’ve managed to translate -p (port mapping) and -v (folder mapping) but where would I put -e.

In his image he has:

-e ENABLE_STARTUP_SCRIPTS=<yes|no> \
-e VPN_USER=<vpn username> \
-e VPN_PASS=<vpn password> \
-e VPN_PROV=<pia|airvpn|protonvpn|custom> \
-e VPN_CLIENT=<openvpn|wireguard> \
-e VPN_OPTIONS=<additional openvpn cli options> \

Would I put that in Container CMD, Container Args or Container Environment Variables??

4

-e should be environment variables

1 Like
5

here’s a list of all options with descriptions

6

Maybe this could help:
https://www.composerize.com/

1 Like
7

Here is what I am using

Links to both docker hub
https://hub.docker.com/r/qmcgaw/gluetun
https://hub.docker.com/r/linuxserver/qbittorrent

this allows you to put anything behind the vpn

networks:
  main:
    name: main
services:
  gluetun:
    container_name: qbit-gluetun
    image: qmcgaw/gluetun:${GLUETUN_VERSION}
    hostname: qbit
    user: 0:568
    ports:
      - 6881:6881 # Torrent
      - 6881:6881/udp # Torrent
      - 8085:8085
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    restart: unless-stopped
    environment:
      - PUID=568
      - VPN_SERVICE_PROVIDER=${VSP}
      - VPN_TYPE=${VT}
      - WIREGUARD_PRIVATE_KEY=${WPK}
      - WIREGUARD_PRESHARED_KEY=${WPSK}
      - WIREGUARD_ADDRESSES=${WGA}
      - SERVER_COUNTRIES=${SC}
      - TZ=${TZ}
      - FIREWALL_OUTBOUND_SUBNETS=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
      - HEALTH_VPN_DURATION_INITIAL=120s
    networks:
      - main
    volumes:
      - ${GLUETUN_DATA}:/gluetun
  qbittorrent:
    container_name: qbittorrent #temporary passowrd in container logs
    image: ghcr.io/linuxserver/qbittorrent:${QBITTORRENT_VERSION}
    restart: unless-stopped
    environment:
      - PUID=set as need
      - PGID=set as need
      - TZ=${TZ}
      - WEBUI_PORT=8085
    network_mode: service:gluetun
    depends_on:
      - gluetun
    volumes:
      - ${QBITTORRENT_CONFIG}:/config
      - ${DOWNLOAD}:/mnt/dl1
8

I would rather have both the qbittorrent and my VPN inside the same container. Less management to do.

What would be the equivalent of – of a Docker image? For example :

--cap-add=NET_ADMIN \
9

The “NET_ADMIN” is to create the tunnel device. it goes hand in hand with, /dev/net/tun:/dev/net/tun

So I would advise you to run those as separate containers…

GLUETUN is only six field to enter one time

These

      - VPN_SERVICE_PROVIDER=${VSP}
      - VPN_TYPE=${VT}
      - WIREGUARD_PRIVATE_KEY=${WPK}
      - WIREGUARD_PRESHARED_KEY=${WPSK}
      - WIREGUARD_ADDRESSES=${WGA}
      - SERVER_COUNTRIES=${SC}

once it is done just create any container you want to use the VPN use network mode
network_mode: service:gluetun

and put the containers ports you want to use on gluetun then you can run one VPN but have any number of containers using it…

It is more flexible because if you get them built together you are married to that one image…(and cant add services) With this method I can change torrent clients any time I please