I am running a few services from a docker-compose file, and on windows they all run fine without issue. However, when running those same services on Linux Fedora host machine, one of the services fail to start properly (without changing anything).
The service in question has an rpc network error (it is an avax cryptocurrency cli):
Any common reason for why a service may run differently on Windows OS Host vs. Linux?
The service could not run on an Ubuntu VM, so I think it may be regardless of Linux distribution.
# Use Ubuntu 20.04 as the base image
FROM ubuntu:20.04 as avalanche-cli
# Set a non-interactive frontend for apt-get to avoid prompts
ENV DEBIAN_FRONTEND=noninteractive
# Update the package list and install dependencies in a single RUN command to reduce layers
RUN apt-get update && \
apt-get install -y \
tzdata \
curl \
python3 \
python3-pip \
expect \
dos2unix && \
# Clean up to reduce image size
apt-get clean && \
rm -rf /var/lib/apt/lists/*
# Install Python pexpect package
RUN pip3 install pexpect
# Download and install the Avalanche-CLI binary
RUN curl -sSfL https://raw.githubusercontent.com/ava-labs/avalanche-cli/main/scripts/install.sh | sh -s -- -b /usr/local/bin
# Set the working directory
WORKDIR /
# Copy the entrypoint script and the Avalanche CLI configuration file into the container
COPY ./docker_scripts/avax.sh /avax.sh
COPY ./config/avax_cli_config.json /avaxconfig/config.json
# Convert line endings to Unix format and make the script executable
RUN dos2unix /avax.sh && \
chmod +x /avax.sh
# Set the entrypoint script to be executed when the container starts
ENTRYPOINT ["/avax.sh"]
No, the avax cli starts all the nodes by default and handles them (I can’t control this). I believe there are 5 nodes total.
So node 2 is within the avax cli, it’s not something I’d very easily be able to directly interact with.