config_files | Backup of my configuration files | Continuous Backup library

in your docker compose i see you are using vpc1, if this is AWS, check your security groups, and allow from which computeror VM, you are connecting to the container from, to be able to access this.

UPDATE: this should be fixed in Docker 20.10.5 so upgrading may be preferable to downgrading!

If you downgrade to Docker 20.10.3 the issue should be resolved. I believe it is a bug introduced in this version as discussed here: https://github.com/moby/moby/issues/42093

Nasty issue! Hoping a fix is released soon...

And if downgrading isn't an option for you, you can try setting the COMPOSE_INTERACTIVE_NO_CLI environment variable (to 1) as discussed here -- e.g. prepend:

/app/log_files is still owned by deployers user inside your container and appuser does not have permission to write to it. As per your comment, it seems /home/deployer/log_files is owned by deployer:deployers with permission drwxr-xr-x. The permissions will be the same for /app/log_files inside container as per bind mount.

Even if deployers user does not exists in your container it will still be owned by the UID of deployers user (you can check this by running ls from inside the container).

You can:

• Add world-writable permission to /home/deployer/log_files such as

Alright, I found a solution! It most certainly is not a perfect solution, but it is a solution.

Unfortunately, I was not able to get it to work on Visual Studio with Windows. I will probably try again at some point, but I think the version of netCDF-cxx4 is out of date on vcpkg or something. I am currently away from my primary work station, so I will have to try again on there to see if I can get a solution in Visual Studio. Anyway, here's what I did that seemed to work:

1. I downloaded Ubuntu 20.04.1 via the Windows Subsystem for Linux (WSL). I'm not sure if this will work for older or newer versions of Ubuntu, but I assume that it will. I also am using the Windows Terminal that they mention on that page and set up my colors with the vimrc example file found here.

This changes how your file system works a bit by adding two layers above C:\, which are /mnt/. You can navigate to your files on Windows by going to /mnt/c/Users/ and to the Ubuntu subsystem by going to /. I named my Ubuntu account usr, so the 'desktop' Ubuntu files are kept in /home/usr. For all of the subsequent steps, I am using the Ubuntu terminal window in the Windows Terminal application.

There was also an issue with installing zlib via vcpkg after enabling WSL, but I don't know how to resolve it nor have I found a solution anywhere.

1. I downloaded a C++ compiler by running sudo apt install build-essential, and installed CMake and netCDF-C via sudo apt install cmake libnetcdf-dev.

2. I installed netCDF-cxx4 by cloning their GitHub repository to my home directory /home/usr and using the commands

It is very possible that the libjpeg library doesn't compile with autotools and/or makefiles in the MinGW tool suite. Even if it is a gcc for Windows, it is not like all the code is fully portable between platforms, and those autotools or Makefiles might do some assumptions of platform that are not correct in Windows.

In general, the Visual Studio toolchain (MSBuild, cl.exe) is better supported in Windows platforms by the community, could be considered the default to-go, especially nowadays that the Visual Studio Community editions are completely free.

The packages in ConanCenter are also typically (and most of them, the ones created from the conan-center-index repo) built and tested with Visual Studio (several versions), so the support is expected to be much better than the one for MinGW.

You cannot use wild card in copy command. You need to first find the directory and then copy.

After much more research I found a solution to this problem. But I had to drop the constraint of using docker-compose.

Currently, I think that what I need to do is not possible with docker-compose because a container once started with docker-compose will always be controlled by docker-compose commands as long as it is online. The reason is that labels can not be changed on running containers and docker-compose finds the container it controls via the labels (see question for details).

So although one could use:

This ServletContext 'null' initialized message is caused by an older MyFaces bug: MYFACES-3356. Unfortunately the Liberty jsf-2.0 implementation doesn't appear to have that fix - it would be worthwhile to open a support ticket with IBM.

As a workaround, if it's workable for your app you can enable application expansion in your server.xml via