portainer: Cannot delete stack and cannot see container in another stack

Bug description 1) I have 2 different bugs with stacks, the first is is that there is this stack i cant delete: image

When i try i get this message: image

The second with another stack that works fine, is’t that the 2 generated containers aren’t visible. I think there is some artifact from the previous stack generated with the same docker yml wich was initially working fine, then it bugged i tried to re-create it with another new.

Containers are visible with “docker container ls”

image.

Portainer version: 2.1.1
Docker version (managed by Portainer): Docker version 20.10.3, build 48d30b5
Platform (windows/linux): ubuntu server 20.04;
Browser: Firefox and opera latest versions

Portainer Logs

pull access denied for mongodb, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied (err=Pulling mongodb (mongodb:)… The image for the service you’re trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

pull access denied for mongodb, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
) (code=500)
2021/02/16 05:59:41 http error: The Compose file '/data/compose/32/docker-compose.yml' is invalid because:
services.discourse.environment contains {"DISCOURSE_USERNAME": "bbc"}, which is an invalid type, it should be a string
 (err=The Compose file '/data/compose/32/docker-compose.yml' is invalid because:
services.discourse.environment contains {"DISCOURSE_USERNAME": "bbc"}, which is an invalid type, it should be a string
) (code=500)
2021/02/16 05:59:53 http error: The Compose file '/data/compose/32/docker-compose.yml' is invalid because:
services.discourse.environment contains {"DISCOURSE_USERNAME": "bbc"}, which is an invalid type, it should be a string
 (err=The Compose file '/data/compose/32/docker-compose.yml' is invalid because:
services.discourse.environment contains {"DISCOURSE_USERNAME": "bbc"}, which is an invalid type, it should be a string
) (code=500)
2021/02/16 06:42:09 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)
2021/02/16 06:42:09 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)
2021/02/16 06:46:08 http error: Unable to proxy the request via the Docker socket (err=context canceled) (code=500)
2021/02/16 11:54:23 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/16 11:54:28 http error: Invalid credentials (err=Unauthorized) (code=422)
2021/02/16 11:54:33 http error: Invalid credentials (err=Unauthorized) (code=422)
2021/02/16 11:54:50 http error: Invalid credentials (err=Unauthorized) (code=422)
2021/02/16 12:41:03 http error: The Compose file '/data/compose/34/docker-compose.yml' is invalid because:
Unsupported config option for wordpress: 'depends_on'
 (err=The Compose file '/data/compose/34/docker-compose.yml' is invalid because:
Unsupported config option for wordpress: 'depends_on'
) (code=500)
2021/02/16 12:41:47 http error: The Compose file '/data/compose/35/docker-compose.yml' is invalid because:
Unsupported config option for wordpress: 'depends_on'
 (err=The Compose file '/data/compose/35/docker-compose.yml' is invalid because:
Unsupported config option for wordpress: 'depends_on'
) (code=500)
2021/02/17 04:26:42 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/17 04:26:43 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/17 04:26:43 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/17 04:26:43 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/17 04:26:43 http error: Invalid JWT token (err=Invalid JWT token) (code=401)
2021/02/17 04:36:53 http error: .FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
 (err=.FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
) (code=500)
2021/02/17 04:37:01 http error: Unable to retrieve Compose file from disk (err=open /data/compose/21/docker-compose.yml: no such file or directory) (code=500)
2021/02/17 04:37:58 http error: .FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
 (err=.FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
) (code=500)
2021/02/17 04:46:08 http error: .FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
 (err=.FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
) (code=500)
2021/02/17 04:50:43 http error: .FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
 (err=.FileNotFoundError: [Errno 2] No such file or directory: '/data/compose/21/docker-compose.yml'
) (code=500)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (2 by maintainers)

Most upvoted comments

Small update if I add proper compose file to requested path I can remove stack so already did. (maybe somebody find this usefull)

Encountered the issue also. Fixed it by

  1. find the id of the stack from the portainer address bar (ex. 7)
  2. ssh and navigate to where the portainer data is stored (/data/compose)
  3. find a folder named after the stack id

at this point you should see the stack id folder and another folder just like it w/ -old at the end

  1. rename the folder with the stack id by appending -bak to the end
  2. rename the folder stack w/ the stack id and -old to just the stack id

At this point try deleting the stack with portainer and it should work. If it does, go ahead and delete the backup made in step 4. In our setup, we’re using the api to check out the code via git but it looks like it was an incomplete checkout. There were folders and files missing which should exist.