`shm_size` setting not respected in Drone 1.0

Drone Support
1

With the following .drone.yml:

pipeline:
  default:
    image: node:10.15-alpine
    shm_size: 2048000000
    commands:
      - df -h /dev/shm

And “Trusted” enabled in the repo on both 0.8 and 1.1, I get differing results:

0.8: "1.9G"

+ df -h /dev/shm
Filesystem                Size      Used Available Use% Mounted on
shm                       1.9G         0      1.9G   0% /dev/shm

1.1: "64.0M"

+ df -h /dev/shm
Filesystem Size Used Available Use% Mounted on
shm 64.0M 0 64.0M 0% /dev/shm

I am not an admin for either installation.

Is shm_size not available to be set in Drone 1.1?

2

Just an FYI for any others who may struggle with this problem: my coworker managed to find a repo online with a workaround for this same issue. A minimal example is as follows:

kind: pipeline
name: default
steps:
  - name: my-step
    image: node:10.15-alpine

    # Use configured in-memory volume in place of /dev/shm
    volumes:
      - name: droneshm
        path: /dev/shm

    commands:
      - # your commands

# This creates a tmpfs volume for the duration of the pipeline
volumes:
  - name: droneshm
    temp: {}
3

Hi!

I’m facing the same behaviour. I’m trying to do some web test using chrome/firefox and I need to set up a /dev/shm larger than 64M.

I tried several options, but seems that shm_size not longer available in drone.

Is there some way to set up the shm_size?

Thanks!
Regards