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
Folllowing the discussion from Issue #77 about recomposing software stacks, CAMP realize replaces every FROM statements from the Dockerfile, and therefore makes multi-stages build invalid.
Steps to reproduce
For instance, consider the java example from samples/java which we modify so that Tomcat has its own component in the camp.yml below:
When we trigger CAMP realize, we get a wrong Dockerfile for the greetings service, which has two stages. See below, both FROM statements now points towards camp-tomcat_0, whereas only the second one should have been updated.
# Step 1: Build the WAR file FROM camp-tomcat_0 as builder
LABEL maintainer "franck.chauvel@sintef.no"RUN apt-get update && \
apt-get install -y --no-install-recommends \
maven=3.3.9-4 && \
apt-get clean && \
rm -rf /var/lib/apt/lists/*
RUN mkdir greetings
WORKDIR /greetings
COPY . /greetings
RUN mvn clean package
RUN mv target/greetings-1.0-SNAPSHOT.war target/greetings.war
# Step 2: Deploy the WAR file into a Tomcat instance FROM camp-tomcat_0
COPY --from=builder /greetings/target/greetings.war /usr/local/tomcat/webapps/greetings.war
CMD ["catalina.sh", "run"]
Characteristics
Description
Folllowing the discussion from Issue #77 about recomposing software stacks, CAMP realize replaces every FROM statements from the Dockerfile, and therefore makes multi-stages build invalid.
Steps to reproduce
For instance, consider the java example from
samples/java
which we modify so that Tomcat has its own component in thecamp.yml
below:When we trigger CAMP realize, we get a wrong Dockerfile for the greetings service, which has two stages. See below, both FROM statements now points towards
camp-tomcat_0
, whereas only the second one should have been updated.Other files and URLs
Relationships
Help on issue template
Preview to follow the link or open file .github/ISSUE_DOC.md
The text was updated successfully, but these errors were encountered: