You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing into a containers writeable layers is typically bad practice for long running applications.
The web application specifically does a volume mount for /tmp. We should likely consider something similar for the containerized server. Likely, a volume /tmp or maybe /tmp/deephaven, which could be bind mounted in our dev setup by default.
If we change the location away from /tmp, we'll want to configure the system property java.io.tmpdir.
It may be possible to configure just /cache/tmp without a new volume, in which case we piggyback off of the existing volume; but this would elevate temporary data to cache-like semantics, which may not be desirable.
Writing into a containers writeable layers is typically bad practice for long running applications.
The web application specifically does a volume mount for
/tmp
. We should likely consider something similar for the containerized server. Likely, a volume/tmp
or maybe/tmp/deephaven
, which could be bind mounted in our dev setup by default.If we change the location away from
/tmp
, we'll want to configure the system propertyjava.io.tmpdir
.It may be possible to configure just
/cache/tmp
without a new volume, in which case we piggyback off of the existing volume; but this would elevate temporary data to cache-like semantics, which may not be desirable.https://docs.docker.com/storage/tmpfs/ would be great, but it only works on Docker for Linux.
The text was updated successfully, but these errors were encountered: