Comments (4)
With readOnlyRootFilesystem
set, it seems even writing files in the OS's default temp dir wouldn't be allowed, at least in my testing with Alpine.
The reason we used .
for the temp dir is because we're using scratch
as the base image. As a result, the container has almost nothing of an OS, not even a temp dir, and basically only holds our Go binary.
If we want to use readOnlyRootFilesystem
, then I think we need to rethink where we keep that cache dir. Maybe we would need a separate volume to store the cache.
from nack.
maybe we should change to the alpine image like in the nats-server?
from nack.
With readOnlyRootFilesystem set, it seems even writing files in the OS's default temp dir wouldn't be allowed, at least in my testing with Alpine.
That's correct. To overcome that you can attach a volume with write permissions under the path of the temp dir.
from nack.
I created a PR for @mionskowski-form3 suggestion ☝️
from nack.
Related Issues (20)
- Container for 0.9.1 is not tagged with the version HOT 2
- Unable to start image when using `/jetstream-controller` path on 0.9.1 HOT 1
- Log all operator events
- Nack doesn't rename streams/consumers
- Release new image on updated Alpine and Go to address vulnerabilities HOT 2
- YAML config doesn't support all time formats on maxAge
- KeyValue management on NACK
- nats-server-config-reloader: Inotify Not Working in K8 with the secrets
- Add support for UserCredentials for consumer HOT 1
- Handling NATS clusters in multiple namespaces HOT 4
- AckWait default value seems to be wrong
- Feature request: Add support for Jetstream domain HOT 2
- Lack of subject update Changing nats filter subjects HOT 15
- Connections to NATS server not closed HOT 5
- When installing according to the manual, jetstreams are NOT enabled HOT 1
- Unable to map the account CRD to the nats server's existing account when creating jetstreams with multi-tenants support HOT 2
- Number of issues with ReadMe manual HOT 1
- When a consumer is deleted from the server, NACK does not recreate it HOT 8
- Error: "failed to connect to nats-servers(nats://nats:4222): nats: secure connection not available" while creating a stream in an account. HOT 1
- NACK gave up on creating a stream before NATS became available
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nack.