a month ago
Hello Railway team,
Please clarify three pre-deployment questions for a Limited Trial account. This is an information-only inquiry; no project or service has been created for this proposed test.
-
What is the actual enforced RAM limit for one Docker service/replica on Limited Trial? The active plan card shows 0.5 GB per service, while the Usage page and trial documentation indicate 1 GB. Which applies, and are these different limits or a display/documentation inconsistency?
-
Is there an official, supported way to deny ALL outbound network traffic from the workload container to destinations outside that container, including IPv4, IPv6 and DNS, while PostgreSQL 18 and its test harness run together inside it and communicate only through a Unix-domain socket? We need an enforceable runtime boundary equivalent to Docker --network none, not merely no public domain/TCP proxy, private networking, disabled IPv6, or restrictions on selected outbound ports. The intended workload uses a non-root user and synthetic data only. Please identify the supported feature and documentation, or explicitly confirm if this isolation is not available on Railway. Please also clarify whether any platform-required external traffic would remain possible from the workload.
-
If such isolation is supported, can a short, single-container test use only existing Limited Trial credits without adding a payment method, upgrading or starting a paid subscription? Are there any mandatory additional charges or plan requirements, and will execution stop when the trial credit is exhausted?
Please provide written clarification only. This request does not authorize deployment, test execution, configuration or permission changes, credit consumption, paid work, or a subscription change. No application source, credentials or private logs are included.
Thank you.
1 Reply
a month ago
We don't offer a supported way to block all outbound traffic from a container on any plan. There is no setting equivalent to Docker --network none, no per-service egress firewall, and no outbound deny or allowlist rule, so the isolation you describe isn't available. The Limited Trial does have restricted outbound network access and a limited set of available ports, but that is a trial restriction, not an isolation feature you can rely on for this.
On RAM, the two figures measure different things. The 1 GB in the plans table is the per-service maximum with replicas added together, and the Trial allows up to 2 replicas, so each replica is capped at 0.5 GB.
On credits, the trial runs on its one-time $5 grant with no payment method or paid plan required. When that grant is used up or 30 days pass, the trial ends and deployments are stopped. Nothing moves to a paid plan unless you choose one, as described in the Free Trial docs.
Status changed to Awaiting User Response Railway • about 1 month ago
24 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 24 days ago