Start here
Your own Dockerfile
Any language, any stack: OceanLaunch builds the Dockerfile in your repository and runs the result.
Create the app
In your workspace choose New app, then Dockerfile from Git. Give the HTTPS address of a repository
on GitHub, GitLab, Bitbucket or Codeberg, a branch (default main), and where the Dockerfile is
(default Dockerfile at the repository root, or a path like api/Dockerfile). Private
repositories work as for every Git app: see Git and deploy on push.
How it's built
- OceanLaunch downloads the commit and builds it with BuildKit. The whole repository is the build context,
so
COPY . .works and your.dockerignoreapplies (leave out.git,node_modules, local secrets). - Multi-stage builds,
RUN --mount=type=cacheand the other BuildKit features work. Build steps can reach the internet (package registries), but nothing inside OceanLaunch, and they never see your app's variables or secrets. - Builds use BuildKit's own, current Dockerfile frontend: a
# syntax=line is ignored. Each app's cache mounts are its own; no other app can read or change them. Images inFROMare always checked with their registry. - A build may take up to 30 minutes, and the finished image may be up to 2 GB.
It must not run as root
Every app on OceanLaunch runs as an unprivileged user. After the build, OceanLaunch checks the image and stops the
deploy if it would run as root. Add a USER line near the end of your Dockerfile:
FROM node:24-bookworm-slim
WORKDIR /app
COPY --chown=node:node . .
RUN npm ci --omit=dev
USER node
CMD ["node", "server.js"]
Images based on Debian or Ubuntu can add a user with
RUN useradd --system --uid 10001 app, then USER app. Make sure that user can write
wherever your app writes.
Port and health check
Set the port your app listens on (any port; 8080 unless you change it). PORT and
SERVER_PORT are set to it. A new version gets traffic once something listens on that port, or, with a
health check path in Settings, once that path answers with a 2xx status. This works even if your image has no
shell or curl.
Deploys
- Deploy latest builds the newest commit on the branch; with the GitHub App, every push does.
- A restart, a stop and start, or adding a domain runs the commit that's running now.
- Change the Dockerfile path on the app's Settings tab; it applies on the next deploy.