Fixes CI pipeline (#204)

After extensions have been renamed, the CI pipeline was still
recognizing previous folder names. This PR fixes the pipeline to only
retrieve the latest updates.
Previously, builds also fail to identify that they are running in docker
and try to set up vscode-related configs.

---------
Co-authored-by: Kelly Guo <kellyguo123@hotmail.com>

.aws/premerge-ci-buildspec.yml

@@ -6,7 +6,7 @@ phases:
       - echo "Launching EC2 instance to run tests"
       - |
         INSTANCE_ID=$(aws ec2 run-instances \
-          --image-id ami-0b3a9d48380433e49 \
+          --image-id ami-0e6cc441f9f4caab3 \
           --count 1 \
           --instance-type g5.2xlarge \
           --key-name production/ssh/isaaclab \
@@ -36,7 +36,6 @@ phases:
           --availability-zone us-west-2a \
           --ssh-public-key file://~/.ssh/id_rsa.pub \
           --instance-os-user ubuntu
-
   build:
     commands:
       - echo "Running tests on EC2 instance"

isaaclab.sh

@@ -22,6 +22,15 @@ export ISAACLAB_PATH="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && p
 # Helper functions
 #==
 
+# check if running in docker
+is_docker() {
+    [ -f /.dockerenv ] || \
+    grep -q docker /proc/1/cgroup || \
+    [[ $(cat /proc/1/comm) == "containerd-shim" ]] || \
+    grep -q docker /proc/mounts || \
+    [[ "$(hostname)" == *"."* ]]
+}
+
 # extract isaac sim path
 extract_isaacsim_path() {
     # Use the sym-link path to Isaac Sim directory
@@ -291,7 +300,7 @@ while [[ $# -gt 0 ]]; do
 
             # check if we are inside a docker container or are building a docker image
             # in that case don't setup VSCode since it asks for EULA agreement which triggers user interaction
-            if [ -f /.dockerenv ]; then
+            if is_docker; then
                 echo "[INFO] Running inside a docker container. Skipping VSCode settings setup."
                 echo "[INFO] To setup VSCode settings, run 'isaaclab -v'."
             else