Container failed to start - volume mount error
indigital-kuba
PROOP

10 months ago

My Docker build completes successfully, but the container fails to start when I add a volume for uploads. Getting this error:

=========================

Container failed to start

=========================

/orchestrator.RouterLegacyService/CreateDeployment UNKNOWN: error creating container: could not parse throttle device at /dev/zvol/railway_0/vol_28zk52hu3hfsclwn: no such file or directory

Setup:

  • Bedrock WordPress with php:8.2-apache
  • Volume mount path: /app/web/app/uploads (I also tried /var/www/html/web/app/uploads)
  • Region: europe-west4
  • Build succeeds, container startup fails

Dockerfile:

FROM php:8.2-apache

# Install system dependencies
RUN apt-get update && apt-get install -y \
    git \
    unzip \
    libzip-dev \
    && docker-php-ext-install zip mysqli pdo pdo_mysql \
    && apt-get clean && rm -rf /var/lib/apt/lists/*

# Install Composer
COPY --from=composer:latest /usr/bin/composer /usr/bin/composer

WORKDIR /var/www/html

# Copy composer files first for better caching
COPY composer.json composer.lock ./

# Install dependencies
RUN composer install --no-dev --optimize-autoloader --no-scripts

# Copy the rest of the application
COPY . .

# Run any post-install scripts
RUN composer run-script post-install-cmd --no-interaction || true

# Configure Apache document root
ENV APACHE_DOCUMENT_ROOT /var/www/html/web

RUN sed -ri -e 's!/var/www/html!${APACHE_DOCUMENT_ROOT}!g' /etc/apache2/sites-available/*.conf && \
    sed -ri -e 's!/var/www/!${APACHE_DOCUMENT_ROOT}!g' /etc/apache2/apache2.conf /etc/apache2/conf-available/*.conf

# Enable mod_rewrite
RUN a2enmod rewrite

EXPOSE 80

The volume ID is vol_28zk52hu3hfsclwn. Looks like a ZFS volume device issue on Railway's side?

Has anyone encountered this?

Solved

3 Replies

Railway
BOT

10 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Railway
BOT

10 months ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!

Status changed to Awaiting User Response Railway 10 months ago


10 months ago

Hello,

The service is back online!

Best,

Brody


Railway
BOT

10 months ago

✅ The ticket Startup issue due to storage error has been marked as completed.


Railway
BOT

10 months 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 10 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...