Update Dockerfile

Dockerfile

@@ -1,99 +1,15 @@
-FROM heartexlabs/label-studio:hf-latest
-
-################################################################################
-#
-# How to Disable Public Account Creation
-# --------------------------------------
-# By default this space allows for the unrestricted creation of new accounts
-# will full access to all projects and data. This is great for trying out
-# Label Studio and collaborating on projects, but you may want to restrict
-# access to your space to only authorized users. Uncomment the following line
-# to disable public account creation for this space.
-#
-# ENV LABEL_STUDIO_DISABLE_SIGNUP_WITHOUT_LINK=true
-#
-# Set secrets in your space to create an inital user, and log in with your
-# provided username and password. Do not set these in your Dockerfile, as they
-# globally visible on a public space.
-#
-# LABEL_STUDIO_USERNAME
-# LABEL_STUDIO_PASSWORD
-#
-# You will need to provide new users with an invitation link to join the space.
-#
-################################################################################
-
-################################################################################
-#
-# How to Enable Configuration Persistence
-# ---------------------------------------
-# By default this space stores all project configuration and data annotations
-# in local storage with Sqlite. If the space is reset, all configuration and
-# annotation data in the space will be lost. You can enable configuration
-# persistence by connecting an external Postgres database to your space,
-# guaranteeing that all project and annotation settings are preserved.
-#
-# Set the following secret variables to match your own hosted instance of
-# Postgres. We strongly recommend setting these as secrets to prevent leaking
-# information about your database service to the public in your spaces
-# definition.
-#
-# ENV DJANGO_DB=default
-# ENV POSTGRE_NAME=<postgres_name>
-# ENV POSTGRE_PORT=<db_port>
-# ENV POSTGRE_USER=<postgres_user>
-# ENV POSTGRE_PASSWORD=<password>
-# ENV POSTGRE_PORT=<db_port>
-# ENV POSTGRE_HOST=<db_host>
-#
-# Uncomment the following line to remove the warning about ephemeral storage
-#
-# ENV STORAGE_PERSISTENCE=1
-#
-# Note that you will need to connect cloud storage to host data items that you
-# want to annotate, as local storage will not be preserved across a space reset.
-#
-################################################################################
-
-################################################################################
-#
-# How to Enable Cloud Storage
-# ---------------------------
-# By default the only data storage enabled for this space is local. In the case
-# of a space reset, all data will be lost. To enable permanent storage, you
-# must enable a cloud storage connector. We also strongly recommend enabling
-# configuration persistence to preserve project data, annotations, and user
-# settings. Choose the appropriate cloud connector and configure the secrets
-# for it.
-#
-# Amazon S3
-# =========
-# STORAGE_TYPE=s3
-# STORAGE_AWS_ACCESS_KEY_ID="<YOUR_ACCESS_KEY_ID>"
-# STORAGE_AWS_SECRET_ACCESS_KEY="<YOUR_SECRET_ACCESS_KEY>"
-# STORAGE_AWS_BUCKET_NAME="<YOUR_BUCKET_NAME>"
-# STORAGE_AWS_REGION_NAME="<YOUR_BUCKET_REGION>"
-# STORAGE_AWS_FOLDER=""
-# 
-# Google Cloud Storage
-# ====================
-# 
-# STORAGE_TYPE=gcs
-# STORAGE_GCS_BUCKET_NAME="<YOUR_BUCKET_NAME>"
-# STORAGE_GCS_PROJECT_ID="<YOUR_PROJECT_ID>"
-# STORAGE_GCS_FOLDER=""
-# GOOGLE_APPLICATION_CREDENTIALS="/opt/heartex/secrets/key.json"
-# 
-# Azure Blob Storage
-# ==================
-# 
-# STORAGE_TYPE=azure
-# STORAGE_AZURE_ACCOUNT_NAME="<YOUR_STORAGE_ACCOUNT>"
-# STORAGE_AZURE_ACCOUNT_KEY="<YOUR_STORAGE_KEY>"
-# STORAGE_AZURE_CONTAINER_NAME="<YOUR_CONTAINER_NAME>"
-# STORAGE_AZURE_FOLDER=""
-# 
-#
-################################################################################
-
-CMD exec label-studio --host=$SPACE_HOST
+# This will start a code-server container and expose it at http://127.0.0.1:8080.
+# It will also mount your current directory into the container as `/home/coder/project`
+# and forward your UID/GID so that all file system operations occur as your user outside
+# the container.
+#
+# Your $HOME/.config is mounted at $HOME/.config within the container to ensure you can
+# easily access/modify your code-server config in $HOME/.config/code-server/config.json
+# outside the container.
+mkdir -p ~/.config
+docker run -it --name code-server -p 127.0.0.1:8080:8080 \
+  -v "$HOME/.config:/home/coder/.config" \
+  -v "$PWD:/home/coder/project" \
+  -u "$(id -u):$(id -g)" \
+  -e "DOCKER_USER=$USER" \
+  codercom/code-server:latest