timescaledb does not run

[marksugar]

I have encountered a problem with ' could not resize shared memory segment`.

images: timescale/timescaledb:latest-pg11-oss

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
2019-05-02 13:35:29.857 UTC [21] FATAL:  could not resize shared memory segment "/PostgreSQL.989869445" to 6928 bytes:
child process exited with exit code 1
initdb: removing contents of data directory "/var/lib/postgresql/data"

$ cat /etc/docker/daemon.json 
{
  "bip": "10.10.10.1/24",
  "default-runtime": "runsc",
  "runtimes": {
      "runsc": {
          "path": "/usr/local/bin/runsc",
          "runtimeArgs": [
             "--network=host",
             "--file-access=shared"
           ]
      }
    }
}

thanks

[fvoznika]

postgres is trying to use fallocate(2) which is not yet implemented in gVisor. Postgres works if I stub it out and pretend that the call succeeded.

I0503 15:34:59.101510    2755 x:0] [  21] postgres X fallocate(0x5 /dev/shm/PostgreSQL.1903734733, 0x0, 0x0, 0x1b10) = 0x0 errno=95 (operation not supported) (1.804µs)

You can recompile with HAVE_POSIX_FALLOCATE undefined to workaround it. Not sure if there is a another way to configure it after it's built. Would this work for you until we implement it?

[ianlewis]

FYI @fvoznika submitted a patch to implement fallocate(2)
https://gvisor.dev/cl/17740