Demo container does not follow the staging image

ℹ️ Support
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud stable on docker on windows 11

Summary of the issue you are facing:

I have a staging container made of sqllite. There I added an admin. Admin added some apps and disabled few others. Admin also added few documents in the skeleton directory.

Then I push it to docker hub using commit and then push.

Then I create a demo container from the image in docker hub.

When the admin logins, it is Not a copy of staging. It contains only the default apps and no additional skeleton documents.

Please help-

Docker compose for staging:

services:
  app-staging:
    image: nextcloud:stable
    container_name: nc-app-staging
    restart: always
    ports:
      - 2000:80 # This port should be same number as that present in caddyfile
    volumes:
      - nc-vol-staging:/var/www/html
    environment:
      OVERWRITEPROTOCOL: https

volumes:
  nc-vol-staging:

Docker hub

docker login
docker commit nc-app-staging myname/nc-staging:latest
docker push myname/nc-staging:latest
2

docker commit doesn’t capture the data volumes (which is where things like apps and config files,.etc for Nextcloud are stored).

The command/tool you’re using only handles what you would otherwise (normally) place within an image via extending the the Dockerfile.

docker commit is mostly a testing tool. It’s not really used in production IMO.

Check out the Docker docs: https://docs.docker.com

Also, check the docs for that particular Nextcloud Docker image: GitHub - nextcloud/docker: ⛴ Docker image of Nextcloud

Depending on your goals, you may also be interested in the Nextcloud AIO image/stack: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

1 Like
3

Actually, my staging container has many apps removed, many settings changed and updates in skeleton folder.

I want to deploy this as an image for demo and production purposes. Staging is where I play with the requirements and needs.

What could be the best way for this, if not commit & push?

4

Are the newly installed app, settings changes or changes in skeleton folder part of volume?

5

The persistent volume(s), as described in the documentation for the micro-services image:

Or, in some cases, you may want to extend the base image and write your Dockerfile that modifies it to your needs (which is described in the docs with examples).

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.