Postgres does not run

[nlacasse]

Needs SysV shared memory support, which is not yet supported.

[dmonay]

Is there a timeline or a public-facing roadmap of when this integration can be expected to be done? Thanks!

[nlacasse]

It's on our roadmap, but we can't commit to any timeline yet. Sorry.

[fvoznika]

Fixed by 18b3ba4

[marksugar]

Can you still open this question?
I have encountered a problem with ' could not resize shared memory segment`.

images: timescale/timescaledb:latest-pg11-oss

timescaledb is open-source time-series database, by postgres

docker run -d timescale/timescaledb:latest-pg11-oss 

$ docker logs -f 03ddc
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

[iangudger]

That looks like a different problem and different database. Can you open a new issue?