tmpfs mounts not full describe in portainer

[rnz]

Description
tmpfs mounts not full describe in portainer
and can't create mounts from portainer by tmpfs

image

Steps to reproduce the issue:

1. create container with tmpfs mounts
   docker service create
   --name testservice
   --mount type=bind,source=/data/service/s0001/db,target=/var/lib/postgresql
   --mount type=tmpfs,target=/tmp
   --mount type=tmpfs,target=/var/tmp
   --mount type=tmpfs,target=/var/run
   --mount type=tmpfs,target=/run
   --network nginx-network
   --mode replicated
   --replicas 1
   docker-repo/testimage

2. go to service details, look at mounts - tmpfs mounts not fully visualisable

Technical details:

• Portainer version: 1.14.0
• Target Docker version: 17.04.0-ce
• Platform: Debian GNU/Linux 9.0 (stretch)
• Command used to start Portainer:

docker service create \
    --name portainer \
    --publish 9000:9000 \
    --constraint 'node.role == manager' \
    --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock \
    --mount type=bind,src=/data/portainer,dst=/data \
    portainer/portainer \
    -H unix:///var/run/docker.sock

• Target Swarm version (if applicable): 17.04.0-ce
• Browser: Any

[deviantony]

@G07cha Have a look at the TaskTemplate.ContainerSpec.Mounts field in the ServiceCreate operation: https://docs.docker.com/engine/api/v1.30/#operation/ServiceCreate

[G07cha]

@deviantony, yeah, I've deleted my previous comment because I've also found that it's possible to do through ContainerCreate.HostConfig.Mounts, so I'll be looking into that.

[rhalff]

Not sure if totally relevant to this issue, but I needed a tmpfs mount to link within portainer and have used the example from the docker site:

docker volume create --driver local \
    --opt type=tmpfs \
    --opt device=tmpfs \
    --opt o=size=100m,uid=1000 \
    foo

It's then selectable just as any volume.

[TheQue42]

I dont know if this is related, and/or a bug in portainer, but when creating frigate containers according to: https://docs.frigate.video/frigate/installation#docker, portainer is not able to duplicate/edit that container, because of the tmpfs (afaik)

Has anybody got a hint on how to solve it?

[lordraiden]

I dont know if this is related, and/or a bug in portainer, but when creating frigate containers according to: https://docs.frigate.video/frigate/installation#docker, portainer is not able to duplicate/edit that container, because of the tmpfs (afaik)

Has anybody got a hint on how to solve it?

Have you tried like this

  frigate:
    container_name: ${frigate_name}
    image: ghcr.io/blakeblackshear/frigate:stable
  # privileged: true
    <<: *config   
    depends_on:
      - homeassistant
    shm_size: "192mb"
    networks:
      eth0:
        ipv4_address: ${frigate_ip}
      ha-netmqtt:
    ports:
      - "5000:5000" # Port used by the Web UI
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "1984:1984" # go2rtc server HA integration
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${dockerdir}/Frigate:/config
      - /mnt/user/Storage/CCTV:/media/frigate
      - type: tmpfs # 1GB of memory
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    environment:
      - FRIGATE_RTSP_PASSWORD
      - PLUS_API_KEY