Tracy_Baker
Starfighter Starfighter
Starfighter
  • 647 Views

DO188 guided lab 4.6 appears to be broken

Jump to solution

Up to Step 3.1, everything works and looks fine. The Step 3.2 says to do this:

1.JPG

When this is done, an AVC alert is generated (which, incidentally, isn't seen when using sudo . . . I discovered this after switching to the root account attempting to start the container there):

2.JPG

However, after setting the SELinux Boolean (I didn't use the -P option because I didn't want to the Boolean to be persistent) and re-running the command to create the container, the container is still not created:

3.JPG

As seen here, I

  • set the Booean (as recommended by sealert)
  • tried to create the container (forgetting it was still there)
  • removed the container
  • created the container (without the --rm option because I didn't want the container removed automtically if it failed)
  • tried to check the logs (there are none)
  • showed that the container isn't running

In a effort to try and figure out what's going on, I rebuilt the gitea image for the root user. I then logged out of student and in as root and tried again, with the same results.

So, I'm a bit stumped. The lab doesn't work and I'm not sure why.

Program Lead at Arizona's first Red Hat Academy, est. 2005
Estrella Mountain Community College
Labels (4)
1 Solution

Accepted Solutions
Chetan_Tiwary_
Moderator
Moderator
  • 635 Views

Hi @Tracy_Baker !

Thanks for reaching out !

We are aware of this bug and it has been resolved by our curiculum development team. However this fix is waiting to be released. 

For the time being, use this workaround and see if this helps :

 The root cause is in this line in the Containerfile:

 

 

RUN dnf install -y git && \
    curl "https://dl.gitea.io/gitea/${VERSION}/gitea-${VERSION}-linux-amd64" -o ${GITEA_BIN_DIR}/gitea && \
    chmod +x ${GITEA_BIN_DIR}/gitea

 

 

The dl.gitea.io server has added a redirect, which makes the curl command fail.

For students trying to work around the issue while waiting for the next release, adding the -L flag to the curl command should solve the issue:

RUN dnf install -y git && \
    curl -L "https://dl.gitea.io/gitea/${VERSION}/gitea-${VERSION}-linux-amd64" -o ${GITEA_BIN_DIR}/gitea && \
    chmod +x ${GITEA_BIN_DIR}/gitea

 

View solution in original post

2 Replies
Chetan_Tiwary_
Moderator
Moderator
  • 636 Views

Hi @Tracy_Baker !

Thanks for reaching out !

We are aware of this bug and it has been resolved by our curiculum development team. However this fix is waiting to be released. 

For the time being, use this workaround and see if this helps :

 The root cause is in this line in the Containerfile:

 

 

RUN dnf install -y git && \
    curl "https://dl.gitea.io/gitea/${VERSION}/gitea-${VERSION}-linux-amd64" -o ${GITEA_BIN_DIR}/gitea && \
    chmod +x ${GITEA_BIN_DIR}/gitea

 

 

The dl.gitea.io server has added a redirect, which makes the curl command fail.

For students trying to work around the issue while waiting for the next release, adding the -L flag to the curl command should solve the issue:

RUN dnf install -y git && \
    curl -L "https://dl.gitea.io/gitea/${VERSION}/gitea-${VERSION}-linux-amd64" -o ${GITEA_BIN_DIR}/gitea && \
    chmod +x ${GITEA_BIN_DIR}/gitea

 

Tracy_Baker
Starfighter Starfighter
Starfighter
  • 620 Views

@Chetan_Tiwary_ 

Thanks!

Program Lead at Arizona's first Red Hat Academy, est. 2005
Estrella Mountain Community College
Join the discussion
You must log in to join this conversation.